Closed FireIP closed 1 month ago
Hey. When you enter the backend and token in the app and click on "Test Backend" you should see a docker log that tells that the endpoint /status was accessed. This is what the app queries to get the status of the backend.
In the docker log you will see an entry every time an endpoint is accessed, therefore I believe the request never reaches the backend.
How is your setup? Do you expose the backend to the internet or you try it locally? Are you sure the entered backend url includes the port 5005?
Thanks for the quick answer I originally exposed the backend to the internet and then locally for testing. After sleeping about it I probably made some stupid mistake moving from global to local.
I found the issue it was a faulty nginx configuration for the exposed test and then I forgot to remove the s from https locally...
Thanks again for your quick response. The app works great.
Great to hear 🙂 Let me know, when you experience any issues.
I set up the backend and Kuma on my server. The logs claim that the backend can connect to Kuma. Now, to the issue: when I try to connect to the backend, it takes a while and then fails with the error: Network error occurred: The request timed out. So, I started tcpdump to see if the packets get forwarded. My capture tells me that the app manages to build and gracefully end a TCP connection, even exchanging some data. Still, the app reports a connection error. There is no output in the docker logs for uptime-buddy-api besides the startup.
I might be going crazy. It is late, and I am probably missing something obvious. Please tell me if there is any way to get more detailed logs, errors, or other info on why the connection fails. Thanks a lot for putting the effort into creating this project and pushing it to Git. If you know which part is failing or why, let me know. I really appreciate any help you can provide.
The tcpdump: