servus michael,
i'm having the same or similar issue as the last poster. running LMS on a raspi4 (raspbian 10) in a docker container which is connected to the host network. so i can access it with 192.168.1.11 (ip of raspi) on the LMS port. which works fine and i did so on several machines yet. recently i installed tailscale (which plain rocks) so the raspi got another network device with the ip of the tailscale network (100.70.x.x) and can be accessed from anywhere. i can access LMS fine with this IP - but get a 'forbidden' for the settings page. which is kind of expected. additionally i figured it would make sense to set this raspi as a relay node on the tailscale network https://tailscale.com/kb/1019/subnets/ (which rocks even more). that way one can access any internal ip (192.168.1.x) from anywhere in the tailscale network without running the tailscale client on every device on the network. so i can use 192.168.1.11:9000 from anywhere - which works - but again i get a 403 for the settings page. annoyingly - set up this way - also when accessing LMS via the local ip on the local network. checking the logs: Code: -------------------- Slim::Web::HTTP::generateHTTPResponse (1022) Access to settings pages is restricted to the local network or localhost: 100.76.xxx.xxx -> 192.168.1.11 (settings/index.html) -------------------- so it would be really cool if there was a way to whitelist IPs/subnets to allow accessing settings. thanks, markus. ------------------------------------------------------------------------ markusk's Profile: http://forums.slimdevices.com/member.php?userid=34020 View this thread: http://forums.slimdevices.com/showthread.php?t=108599 _______________________________________________ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
