Amazon EC2 set-up failure about outline-server HOT 20 CLOSED

Thanks for the feedback, and sorry for your trouble.

When you run docker ps, does it show a shadowbox container? That's the core of the service.

You can get the JSON needed to set up the Server Manager with

cat /root/shadowbox/persisted-state/shadowbox_server_config.json

(Don't share the output of that with anyone)

If you'd like to try again, the server installation on EC2 was tested using the image ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20180126 - ami-66506c1c (from Community AMIs)

What we did to get it working was:

1. Under "Configure Security Group", added a "Custom TCP Rule" and a "Custom UDP Rule". Set the Port Range for both to 1024-65535, and Source to 0.0.0.0/0

2. Install Docker

   1. SSH in as user "unbuntu"
   2. curl -sS https://get.docker.com/ | sh
   3. sudo usermod -aG docker $USER

3. Reboot machine, then SSH again and run:
   wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh | bash
   Ignore the error:

ERROR: You need to be root to run this script
You have ufw enabled on your machine, please check your configuration to ensure access to high numbered ports.

Because "ufw status" requires "sudo", we accidentally think that ufw is enabled when it is not by default

Could you try that and let us know if it still doesn't work?

from outline-server.

Shadowbox is running, but I don't have the JSON file.

This is my version of Ubuntu.

from outline-server.

I tried again. It works without any problem if I choose your type of machine and follow your instruction.
Thank you, fortuna.

from outline-server.

@fortuna
Good day!
As I understood, outline will automatically add allowed ports to ufw?
Now I need to add them manually.

from outline-server.

Tried Outline installation on ubuntu 16.04 Azure cloud.
The installation script halts at Starting Watchtower ......................... OK.

FYI, I've disabled ufw..
What could be the reason?

from outline-server.

@hybtoy : Unfortunately manually installed Outline servers do not open the ports automatically, but that's something we'd like to do (or create a shadowsocks reverse proxy that allows everyone to use a single port). It's a hard problem because each platform has its own way of controlling traffic, sometimes in cloud platforms it's even completely outside the server.

As a workaround you can write a script that find the port numbers with cat /root/shadowbox/persisted-state/shadowbox_config.json and opens the port according to the platform you use.

from outline-server.

Azure Cloud update - Solved.

An issue with Inbound - Outbound rules. Once we set it properly for ports 1024-65535 it works properly

from outline-server.

I'm having a similar issue, likely from not having UFW even installed on my server. The install hangs after starting the watchtower container. However, I SIGINT the install process and docker ps shows that shadowbox is running. But, this is what I get when I try to pull the config information from the container:
docker exec -it shadowbox cat /root/shadowbox/persisted-state/shadowbox_server_config.json cat: can't open '/root/shadowbox/persisted-state/shadowbox_server_config.json': No such file or directory

EDIT: It should be known that I am running Ubuntu Server 14.04.5 on a Scaleway VPS in Amsterdam.

from outline-server.

I am having the same problem as DonaldKBrown on Ubuntu 17.10 on a HyperV VM. It hangs when starting the watchtower container, shadowbox is running but I cannot get the json configuration.

PS: I got it to work by opening ports 40000-50000 on my Google Wifi (I am running it at home). The install script then finishes. It works really well on Android phone. Trying Chromebook next.

PS2: Creating and sharing keys for others doesn't work for me - the clients cannot connect. Not a big thing since I mainly want to use it myself and my family.

from outline-server.

Alright, I feel silly. I had inadvertently reinstalled ufw. Removing that again fixed my issue. If anyone else has an issue running the installer again after exiting it, you have to stop and remove the previous Docker containers. Run the following commands to do so (ONLY IF YOU HAVE NO OTHER DOCKER CONTAINERS)

docker stop $(docker ps -aq)
docker rm $(docker ps -aq)

from outline-server.

@arunkumar339 Could you elaborate on how you solved the problem seeing that ufw was disabled when your first encountered the issue. I am having the same problem although I am running Ubuntu on my own machine.

from outline-server.

from outline-server.

from outline-server.

from outline-server.

from outline-server.

@zl1775 Sorry you've been having problems connecting to your server. Yes, we do recommend opening all ports above 1024. Were you able to resolve this?

from outline-server.

@markusmobius Happy to hear you got connected. Regarding the new access keys you created, they were probably outside the range of 40000-50000. Yes, we currently recommend opening all ports above 1024.

from outline-server.

@DonaldKBrown Happy to hear you got connected. We are considering a check for the installation script for whether either Docker container already exists.

from outline-server.

@arunkumar339 Happy to hear you got connected!

from outline-server.

Seems like most people here got connected, so I'm going to close this. Please open a new issue for any further manual installation woes!

from outline-server.