search

owntracks / quicksetup

A (mostly) automated installer for OwnTracks Recorder, Frontend with MQTT and Let's Encrypt
https://owntracks.org/booklet/guide/quicksetup/
14 stars 4 forks source link

Frontend not populated after Quicksetup #62

Closed nlanfran closed 2 days ago

nlanfran commented 2 days ago

Hello everybody,

I finally managed to switch away from my previously used HiveMQ broker, and install Mosquitto to my RPi 4.

I followed the quicksetup instructions and was able to complete the installation successfully. But it seems that I have a problem with the Frontend. I wasn't sure whether to post my problem here or to the Frontend section, but seen that I followed the quicksetup script, I try to post it here.

I can connect to my nginx web server using the credentials generated during the quicksetup, and I can see the list of friends (and myself) from the device table. I can also see them in the live map. When I open the frontend, I am in the middle of the ocean, with lat=0 and long=0. I was expecting at least to see the current location for the list of friends, but there is nothing. Layer settings are all checked.

Not sure if this behavior is correct.

The recorder seems to be working, and all the files in the locations '/var/spool/owntracks/recorder/store' are populated with the MQTT messages.

Any idea how to debug it ?

Many thanks for your help.

Nick

jpmens commented 2 days ago

moving to quicksetup

jpmens commented 2 days ago

this might be turning into a faq ...: please look at https://github.com/owntracks/quicksetup/issues/57 (no need to reboot)

jpmens commented 2 days ago

or the bottom of https://github.com/owntracks/quicksetup/issues/61

nlanfran commented 2 days ago

I was able to fix it by changing the baseUrl value inside '/usr/share/nginx/html/owntracks/frontend/config/config.js': internal IP address instead of the DDNS one. Strange, because I tried it already before posting the problem, and even rebooted the RPi. But this alone did not fix it.

The other thing that I added was to open and redirect the port 443 to my RPi. Maybe that was the last step that was missed ??

Many thanks again.

Nick

jpmens commented 2 days ago

HTTPS requires port 443, so yes.