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
Hello,
I am trying to setup fitcrack with a reverse proxy, in this case its NGINX.
So that a user would go from the internet to SERVER.REP(running NGINX) to another server (call it SERVER.FIT running fitcrack using docker), these 2 servers are connected to each other over a virtual LAN (using zerotier)
I am able to load the web page, however when attempting to log in I get the "API server unreachable" popup, its attempting to access the backend via http://SERVER.REP.DOMAIN.TLD:5000/ is there a way to change this?
can anyone guide on how to properly set up fitcrack with SSL using NGINX?
More notes: both servers are running on debian11.
Trying to access the SERVER.FIT directly works as intended and there are no issues.
the NGINX config on SERVER.REP: https://pastebin.com/qGyyxfqJ
The text was updated successfully, but these errors were encountered:
same situation here.
everything is configured and works fine when accessing from local network.
whenever I try to go through nginx from outside, the webfront tries to connect to API using the same OUTSIDE header (fqdn instead of IP). It would be great if we could hardcode the server name so it is always being accessed through local network
Hello,
I am trying to setup fitcrack with a reverse proxy, in this case its NGINX.
So that a user would go from the internet to SERVER.REP(running NGINX) to another server (call it SERVER.FIT running fitcrack using docker), these 2 servers are connected to each other over a virtual LAN (using zerotier)
I am able to load the web page, however when attempting to log in I get the "API server unreachable" popup, its attempting to access the backend via http://SERVER.REP.DOMAIN.TLD:5000/ is there a way to change this?
can anyone guide on how to properly set up fitcrack with SSL using NGINX?
More notes: both servers are running on debian11.
Trying to access the SERVER.FIT directly works as intended and there are no issues.
the NGINX config on SERVER.REP: https://pastebin.com/qGyyxfqJ
The text was updated successfully, but these errors were encountered: