search

PolaricServer / webapp2

Re-write of client app. Based on OpenLayers 5+
GNU Affero General Public License v3.0
15 stars 4 forks source link

Some map interface pieces don't work if not on port 80 #41

Closed mattbk closed 1 year ago

mattbk commented 1 year ago

I installed initially on a Raspberry Pi 2 with nginx, which was preventing apache2 from starting. So I changed port 80 to port 8080 following https://ubiq.co/tech-blog/how-to-change-port-number-in-apache-in-ubuntu/.

At localhost:8080/aprs, the map interface shows up, but all menu buttons don't work--can't log in, can't see Main menu dropdown, etc.

If I stop nginx and put apache2 back on port 80, the map loads fine and things work, as far as I can tell.

Hopefully this is something that can be made more flexible. I think I am able to uninstall nginx and not affect anything I have running on this pi now, but others may need it for some reason.

Edited to add: I think this might be related to why I can't redirect a subdomain to this application using YuNoHost; the results are similar.

Thanks for the hard work on this!

ohanssen commented 1 year ago

Did you edit /etc/polaric-webapp2/config.js ? You can uncomment and edit the first setting (SERVER) using an explicit URL with port number. By default it uses localhost with port 80.

It is probably not impossible to use nginx as a frontend. Except for the mapcache apache plugin it is probably not hard to do that. I haven't tried nginx though.

mattbk commented 1 year ago

Checking in to say I saw your reply, I just haven't made time to mess with this more. Thanks!