8000 Running fitcrack with a reverse proxy(NGINX) · Issue #77 · nesfit/fitcrack · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Running fitcrack with a reverse proxy(NGINX) #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our 8000 terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Pareid0lia opened this issue Mar 29, 2023 · 1 comment
Open

Running fitcrack with a reverse proxy(NGINX) #77

Pareid0lia opened this issue Mar 29, 2023 · 1 comment
Assignees

Comments

@Pareid0lia
Copy link

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

@lukaszzyla
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
0