Can't connect to server / Logs + docker-compose included #1264
Answered
by
proactivematter
proactivematter
asked this question in
Q&A
-
shlink-web-client versionStable How do you use shlink-web-clientSelf-hosted SummaryHaving a really hard time getting this to work! After all is said and done, shlink fails to connect to server. Here are the logs with SHELL_VERBOSITY=3: Here's my docker-compose... Thank you. |
Beta Was this translation helpful? Give feedback.
Answered by
proactivematter
Aug 9, 2024
Replies: 1 comment 5 replies
-
|
All I can see in those logs is a working combination of Shlink, shlink-web-client and the database, but with zero traffic. Can you elaborate on what you mean by "can't connect to server"? What error do you see? Where do you see it? What have you tried? |
Beta Was this translation helpful? Give feedback.
5 replies
-
Unfortunately still missing the key piece of information, which is what error do you get, and where. If you see the error in the web browser, try checking the browser console. If you see an error there, try to look for it in https://shlink.io/documentation/troubleshooting/ |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, I see... I did not think of looking in the browser console for any errors. Indeed, here it is and This happens for all of the url variations I mentioned previously, both with HTTPS enabled/disabled. I looked at the documentation you link, and it seems to be this, right? I don't have a reverse-proxy running. I have cloudflared, but even then I should at the very least have local access working, right? Please let me know. Thanks for the help. |
Beta Was this translation helpful? Give feedback.
-
Cloudflare IS a reverse proxy 😅 |
Beta Was this translation helpful? Give feedback.
-
|
Ah, you're right sorry, didn't think that was the case. Good news, I figured it out after a lot of troubleshooting. I was fundamentally confused about how shlink works, and the fact that I needed to set up separate reverse proxies for both the backend and the frontend. After doing so, everything appears to be working. In fact, I thereafter realized I don't even need to self-host the frontend. Thank you for your quick replies @acelaya. |
Beta Was this translation helpful? Give feedback.
Answer selected by
proactivematter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ah, you're right sorry, didn't think that was the case.
Good news, I figured it out after a lot of troubleshooting. I was fundamentally confused about how shlink works, and the fact that I needed to set up separate reverse proxies for both the backend and the frontend. After doing so, everything appears to be working.
In fact, I thereafter realized I don't even need to self-host the frontend.
Thank you for your quick replies @acelaya.