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

Needs https to use? #15

Closed
ghost opened this issue Oct 4, 2022 · 3 comments
Closed

Needs https to use? #15

ghost opened this issue Oct 4, 2022 · 3 comments

Comments

@ghost
Copy link

ghost commented Oct 4, 2022

I'm running this proxy via my own network, it works flawlessly other than it needs https. How would I fix this?
(please dm me on Discord when you respond because I'm not active on github) My Discord is Skrill#0001
image

@BrodySalvucci
Copy link

I’m not sure so don’t hold me to it, but I believe that it needs to be an actual link (https://www.yourdomain.com) instead of a ip (127.0.0.1).

You could use a service that automatically gives you a HTTPS link not a HTTP link. I am sorry for not using the right terminology for some of these things but I believe that this will help you out.

@e9x
Copy link
Collaborator

e9x commented Oct 9, 2022

I'm running this proxy via my own network, it works flawlessly other than it needs https. How would I fix this? (please dm me on Discord when you respond because I'm not active on github) My Discord is Skrill#0001 image

You can setup NGINX as a reverse proxy, however you will need a signed certificate otherwise you will run into weird bugs relevant to Chromium and the certificate being self-signed. I recommend Let's Encrypt via certbot. Alternatively, you can use Cloudflare to proxy your server and provide HTTPS.

If you cannot get your hands on a signed certificate, perhaps you just want to run website-aio on the client of your instance (if possible). If that isn't possible, there are still CI tools that will host website-aio and provide SSL certificates for you.

@e9x
Copy link
Collaborator

e9x commented Oct 9, 2022

I’m not sure so don’t hold me to it, but I believe that it needs to be an actual link (https://www.yourdomain.com) instead of a ip (127.0.0.1).

You could use a service that automatically gives you a HTTPS link not a HTTP link. I am sorry for not using the right terminology for some of these things but I believe that this will help you out.

SSL certificates can be issued to IP addresses. I believe Let's Encrypt covers this too.

@e9x e9x closed this as completed Oct 10, 2022
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

2 participants