Skip to content
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 terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

https://ficsit-rmd.vercel.app/ doesn't work for remote dedicated server #2

Open
mklierman opened this issue Jan 19, 2024 · 4 comments

Comments

@mklierman
Copy link

I've configured my session on https://ficsit-rmd.vercel.app/ to use the remote IP but it says it can't connect. If I run the dashboard locally on my machine I can connect to the remote IP, however.

@Aiglenoir77
Copy link

Hello, i have se same probleme with Mklierman with my dedicated server

@Jonathan-Hofmann
Copy link
Owner

Hey @mklierman and @Aiglenoir77 thanks for submitting the issue!

I will have a look at the issue! Sadly I cannot fix it in the near future as I dont have much time right now :/

When I have time again I will try to fix this bug :)

@demonbane
Copy link

The problem is that most browsers will not allow a connection from a secure page to an insecure one by default (except for local connections). Since we're connecting to ficsit-rmd over HTTPS, any connection to FRM would need to be HTTPS as well which doesn't work. There are a few different workarounds available.

  1. Easiest: Just allow insecure connections from ficsit-rmd.vercel.app in your browser. In Chrome-based browsers, click the padlock in the address bar, go to Site settings, Insecure content, and set it to Allow.
  2. If you can establish an SSH connection to the remote server, you can just forward the remote port to your local machine so that you'll still be connecting to "127.0.0.1" technically, which will work around the browser restriction.
  3. You can set up a reverse proxy secured with an SSL certificate and point it to FRM and then it should work.

@demonbane
Copy link

Actually, option 3 wouldn't work since ficsit-rmd doesn't support changing the protocol, so it would still be trying an HTTP connection anyway. If that could be added then a reverse proxy would be a viable (and mostly secure) solution.

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

4 participants