Unable to connect to SEPIA host with web app

[edenerium]

Hi Florian!

This project has been a lot of new territory for me, so I don't really understand what I'm doing. I'll try my best to describe my issue to you. I'm sure I just missed a step somewhere

I'm setting up my raspberry pi 3b+ as the sepia host, and I've been successful for the most part so far. Where I'm having trouble is (I think?) is connecting with a client. In my first run of setting up, I went through the process of getting the Let's Encrypt SSL certificate, but once I was running into issues, I cleared the old configs with option 5 of setup-nginx.sh and tried setup without SSL certificate (option 2).

I'm able to reach http://sepia-home.local:20726 on my laptop just fine, it says "welcome to nginx" and all that. http://sepia-home.local:20726/sepia however, does not work. It returns with error 404. I tried on the android app too for good measure, and it gives me "the server does not answer". Pls help :P what am I missing?

EDIT: I should add, when I was first having issues with https, it did work briefly, and I was able to get to the log in screen and log in. I don't know what I did to get it to work, but I can't replicate it haha

[fquirin]

Hi @edenerium ,

sorry for the late reply, I took some days off 🏖️ .

I went through the process of getting the Let's Encrypt SSL certificate, but once I was running into issues

Since you are still a bit unfamiliar with the whole project I'd suggest to skip Let's Encrypt for a while until you feel more comfortable with the server stuff. Opening up your server to the public should be done when everything has been tested, is working and is secured.

I cleared the old configs with option 5 of setup-nginx.sh and tried setup without SSL certificate (option 2).

👍 . I recommend to switch to the self-signed option after we've fixed your current issue. Although it can be a bit tricky to get the certificates imported into your client (Desktop browser, Android app etc.) it will avoid problems with secure origin/mixed-content (non-HTTPS URL) that can for example prevent the microphone from working.

I'm able to reach http://sepia-home.local:20726/ on my laptop just fine, it says "welcome to nginx" and all that. http://sepia-home.local:20726/sepia however, does not work. It returns with error 404. I tried on the android app too for good measure, and it gives me "the server does not answer". Pls help :P what am I missing?

http://sepia-home.local:20726/sepia alone is not a valid path. You probably mean either http://sepia-home.local:20726/sepia/assist/ping (check connection), http://sepia-home.local:20726/sepia/assist/app/ (client app) or http://sepia-home.local:20726/sepia/assist/tools/ (admin app) ?
http://sepia-home.local:20726/sepia should work inside the Android app though as "hostname" or in your Desktop browser.
If it doesn't work you can try the IP address instead as "hostname" like 192.168.0.10 or http://192.168.0.10:20726/sepia (replace the IP with the one of your Raspberry Pi).

Let me know if any of this helps :-)