Get apiURL back of current running Outline Server

[abilovelchin]

apiUrl doesn't exists in /opt/outline/access.txt. Only certSha256 is exists here

When I run sudo bash -c "$(wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh)" code in terminal, I get the following output

[root@vmi93429 /]# sudo bash -c "$(wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh)" Verifying that Docker is installed .......... OK Verifying that Docker daemon is running ..... OK Creating persistent state dir ............... OK Generating secret key ....................... OK Generating TLS certificate .................. OK Generating SHA-256 certificate fingerprint .. OK Writing config .............................. OK Starting Shadowbox .......................... [root@vmi93429 /]#

Please help me. I think that, problem is in security of my server

[Sagit01]

there is a file access.txt.bak in the same folder, I have apiUrl info there

[bemasc]

It looks like the first problem here is that the setup script crashed without an error message. I will try to add an error printout to give us more info about unexpected crashes.

[rahmati]

Facing the same issue on an Amazon LightSail instance. access.txt and access.txt.bak only include certSha256. The server however is functioning correctly for existing keys. I really want to avoid reinstalling (and having to reissue existing keys) if possible. Any ideas on how I can recover apiUrl?

[MutlaqAldhbuiub]

Facing the same issue on an Amazon LightSail instance. access.txt and access.txt.bak only include certSha256. The server however is functioning correctly for existing keys. I really want to avoid reinstalling (and having to reissue existing keys) if possible. Any ideas on how I can recover apiUrl?

I have the same issue, I searched the whole internet for a solution "no apiUrl in /opt/outline/access.txt" but I didn't find any helpful solution. so I take a risk of reinstalling the application by applying this command sudo bash -c "$(wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh)"

sudo bash -c "$(wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh)"
> Verifying that Docker is installed .......... OK
> Verifying that Docker daemon is running ..... OK
> Setting PUBLIC_HOSTNAME to external IP ...... OK
> Creating persistent state dir ............... OK
> Generating secret key ....................... OK
> Generating TLS certificate .................. OK
> Generating SHA-256 certificate fingerprint .. OK
> Writing config .............................. OK
> Starting Shadowbox .......................... FAILED
> The container name "shadowbox" is already in use by another container. This may happen when running this script multiple times. We will attempt to remove the existing container and restart it. Would you like to proceed? [Y/n] Y
> Removing shadowbox container ................ OK
> Restarting shadowbox ........................ OK
> Starting Watchtower ......................... FAILED
> The container name "watchtower" is already in use by another container. This may happen when running this script multiple times. Would you like to replace this container? If you answer no, we will proceed with the remainder of the installation. [Y/n] n
OK
> Waiting for Outline server to be healthy .... OK
> Creating first user ......................... OK
> Adding API URL to config .................... OK
> Checking host firewall ...................... OK

CONGRATULATIONS! Your Outline server is up and running.

To manage your Outline server, please copy the following line (including curly
brackets) into Step 2 of the Outline Manager interface:

{"apiUrl":"https://URL:54277/CODE","certSha256":"8***F3*****EB812E****FC2***9"}

If you have connection problems, it may be that your router or cloud provider
blocks inbound connections, even though your machine seems to allow them.

Make sure to open the following ports on your firewall, router or cloud provider:
- Management port 54277, for TCP
- Access key port 15047, for TCP and UDP

Nothing has been removed or changed for me, also my /opt/outline/access.txt now including apiUrl

** I'm is not responsible for damages that may occur ;P **

[rahmati]

Facing the same issue on an Amazon LightSail instance. access.txt and access.txt.bak only include certSha256. The server however is functioning correctly for existing keys. I really want to avoid reinstalling (and having to reissue existing keys) if possible. Any ideas on how I can recover apiUrl?

I have the same issue, I searched the whole internet for a solution "no apiUrl in /opt/outline/access.txt" but I didn't find any helpful solution. so I take a risk of reinstalling the application by applying this command sudo bash -c "$(wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh)"

sudo bash -c "$(wget -qO- https://raw.githubusercontent.com/Jigsaw-Code/outline-server/master/src/server_manager/install_scripts/install_server.sh)"
> Verifying that Docker is installed .......... OK
> Verifying that Docker daemon is running ..... OK
> Setting PUBLIC_HOSTNAME to external IP ...... OK
> Creating persistent state dir ............... OK
> Generating secret key ....................... OK
> Generating TLS certificate .................. OK
> Generating SHA-256 certificate fingerprint .. OK
> Writing config .............................. OK
> Starting Shadowbox .......................... FAILED
> The container name "shadowbox" is already in use by another container. This may happen when running this script multiple times. We will attempt to remove the existing container and restart it. Would you like to proceed? [Y/n] Y
> Removing shadowbox container ................ OK
> Restarting shadowbox ........................ OK
> Starting Watchtower ......................... FAILED
> The container name "watchtower" is already in use by another container. This may happen when running this script multiple times. Would you like to replace this container? If you answer no, we will proceed with the remainder of the installation. [Y/n] n
OK
> Waiting for Outline server to be healthy .... OK
> Creating first user ......................... OK
> Adding API URL to config .................... OK
> Checking host firewall ...................... OK

CONGRATULATIONS! Your Outline server is up and running.

To manage your Outline server, please copy the following line (including curly
brackets) into Step 2 of the Outline Manager interface:

{"apiUrl":"https://URL:54277/CODE","certSha256":"8***F3*****EB812E****FC2***9"}

If you have connection problems, it may be that your router or cloud provider
blocks inbound connections, even though your machine seems to allow them.

Make sure to open the following ports on your firewall, router or cloud provider:
- Management port 54277, for TCP
- Access key port 15047, for TCP and UDP

Nothing has been removed or changed for me, also my /opt/outline/access.txt now including apiUrl

** I'm is not responsible for damages that may occur ;P **

Thanks for the reply! My search hasn't yield out anything either. I think I'll end up doing the same given the lack of response.

[rahmati]

Update: Reinstalling worked successfully without removing existing keys. Thank you @MutlaqAldhbuiub!