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

Running with self-signed cert in local network #237

Open
michielbdejong opened this issue Dec 17, 2020 · 0 comments
Open

Running with self-signed cert in local network #237

michielbdejong opened this issue Dec 17, 2020 · 0 comments

Comments

@michielbdejong
Copy link

Hi!

I'm trying to run your docker image on https://server inside a local testnet, and running into three problems:

  • the is_http check looks at SEAFILE_SERVER_LETSENCRYPT=true, but setting that (obviously) makes it try to run a letsencrypt script which then complains that 'server' isn't a FQDN. I think I succesfully worked around that by editing line 89 of /scripts/bootstrap.py (here)
  • even then, I run into validate_server_ip failures. So I switched to using https://server.com inside the testnet, and now the server boots up successfully
  • even with these changes, it seems to be using port 80 in /etc/nginx/sites-enabled/seafile.nginx.conf and /etc/nginx/nginx.conf.

Any help or guidance greatly appreciate, but I mainly just wanted to document this issue here, and the steps I'm taking to resolve it. I'll investigate further and report here if I get it working on https://server.com with a self-signed cert inside a local network, without reaching out to LetsEncrypt.

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

No branches or pull requests

2 participants