You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While i'm not sure what monster would port scan, and find the feeder service if it is publicly accessible and dispense all food! However, I figured adding nginx passwords using a .htpasswd was sufficient enough.
I solved this ultimately by allowing a 3rd port, 8443 that is an exact copy of the :443 server binding, with just a small edit of
Looks like the feeder uses the API :443 for health checks? Adding a password directive here seems to cause the feeder to stop phoning home and become unresponsive.
I run petnet on my local network, however, I use DynamicDNS and port forwarding (custom port -> 8443 exposed to the world) to allow access from my mobile phone. I have two cats, and a Nest cam to monitor the bowl and I like the ability to just manually feed based on how much is visible.
The system runs great on Ubuntu 18.04 on a small VM, and Raspberrypi pi-hole to intercept DNS and reroute to the VM.
The text was updated successfully, but these errors were encountered:
yevdev
changed the title
HTTP Basic password auth need extra port for nginx
[Suggestion] HTTP Basic password auth need extra port for nginx
Jun 20, 2021
While i'm not sure what monster would port scan, and find the feeder service if it is publicly accessible and dispense all food! However, I figured adding nginx passwords using a .htpasswd was sufficient enough.
I solved this ultimately by allowing a 3rd port, 8443 that is an exact copy of the :443 server binding, with just a small edit of
Small notes
The system runs great on Ubuntu 18.04 on a small VM, and Raspberrypi pi-hole to intercept DNS and reroute to the VM.
The text was updated successfully, but these errors were encountered: