I used to access my internal services like example.com:6868 and bar.example.com:6969. I had or two sudomains like fubar.example.com and foobar.example.com. But with the wonders of nginx, I was able to proxy everything so I could stop using ports.
All was well until suddenly I couldn't access any sites from **inside** my network. I could access it outside. I could ping the ip and the FQDN. But I couldn't browse to it. A reboot of the router and the problem went away. But it came back a few hours later. And again. And again.
I complained to eero (the router mfg) but now that I think about it, nginx is probably the culprit as things were running well until it's introduction several days ago. I suspect that **something** is happening on a schedule that is causing the problem. If I were to catch the second the problem started, are there log files of everything that is going on at that instant?
All was well until suddenly I couldn't access any sites from **inside** my network. I could access it outside. I could ping the ip and the FQDN. But I couldn't browse to it. A reboot of the router and the problem went away. But it came back a few hours later. And again. And again.
I complained to eero (the router mfg) but now that I think about it, nginx is probably the culprit as things were running well until it's introduction several days ago. I suspect that **something** is happening on a schedule that is causing the problem. If I were to catch the second the problem started, are there log files of everything that is going on at that instant?