Describe the bug
I set up the Filament manager on two of my systems and use a shared postgresql database on a third system (my home server).
I routed both OctoPrint instances to the internet via a reverse proxy.
No I wanted to check how much filament is on one of my printers and I can't see any of the spools I have in my database.
It seems like the database connection is made from the client, not from the server.
Steps to reproduce
Use external SQL database
add spools
use Octoprint from outside your network via reverse proxy
try to select a spool
Expected behavior
The connection to the database should be done from the server, not from the client so you can also use the printer when you are outside of your network and don't want to open the ports to postgresql in your router.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Describe the bug I set up the Filament manager on two of my systems and use a shared postgresql database on a third system (my home server). I routed both OctoPrint instances to the internet via a reverse proxy. No I wanted to check how much filament is on one of my printers and I can't see any of the spools I have in my database.
It seems like the database connection is made from the client, not from the server.
Steps to reproduce
Expected behavior The connection to the database should be done from the server, not from the client so you can also use the printer when you are outside of your network and don't want to open the ports to postgresql in your router.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.