Skip to content

Instantly share code, notes, and snippets.

@laruche
Created July 9, 2021 10:16
Show Gist options
  • Save laruche/3286f31fe604e04711eb0a7965855948 to your computer and use it in GitHub Desktop.
Save laruche/3286f31fe604e04711eb0a7965855948 to your computer and use it in GitHub Desktop.
@uhlhosting
Copy link

Hey @uhlhosting, did you set your Container Port to 8080? I literally just tested this earlier and it works. You do have to wait upwards of 30 or more seconds for the app to become available after the change.

Hi @maietta You mean here?

image

@uhlhosting
Copy link

I tried it, yet for me does manages to get to a 404 missing page, when I turn on http to https is back on 502 error.

@maietta
Copy link

maietta commented Aug 6, 2022

Yes, @uhlhosting. That is the place you need to set port to 8080.

The 404 page IS the application running correctly.

Your next step I believe is to log into your server via SSH and find the container to run the command to generate the API key that you will use to begin using this application, as outlined in the official docs for this application.

Some applications will generate a new API key on the first run and reveal it early in the logs but this application is not one of them. They designed it so you have to run a command against a running container. Sadly, the name is not predictable so you have to find the container name by running another command.

Once you SSH into your machine running Caprover, run docker ps ls | grep shlink to find the container name.

Then run docker exec -it my_shlink shlink api-key:generate, replacing "my_shlink" with the unique name of your container, as outlined in this document: https://shlink.io/documentation/install-docker-image/.

Like so:

image

@uhlhosting
Copy link

@maietta thanks for the explaining, I managed to generate the API key too, yet still when I add it in the web ui app, it gives error.

@uhlhosting
Copy link

I think I got it working in app.shlink.to, would be nice to add this too in caprover.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment