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

Certbot renewal failure + exposed ports #6

Open
fturmel opened this issue Jan 5, 2025 · 1 comment · May be fixed by #7
Open

Certbot renewal failure + exposed ports #6

fturmel opened this issue Jan 5, 2025 · 1 comment · May be fixed by #7

Comments

@fturmel
Copy link

fturmel commented Jan 5, 2025

Thanks for sharing this with the community @leerob. Couple issues I wanted to point out:

Certbot renewal

It appears that your nginx/certbot setup is not able to handle automated renewals. I didn't look too carefully but it might be that you need to manually set up an acme-challenge block in the nginx config.

CleanShot 2025-01-05 at 10 35 56@2x

Exposed ports

Another issue I noticed is that your setup is exposing the app and db to the world. Usually you'd want to only expose TCP 80 and 443, and UDP 443 (for http/3).

Here are some ways to improve this:

CleanShot 2025-01-05 at 11 06 15@2x

@fturmel
Copy link
Author

fturmel commented Jan 5, 2025

Oh, and while we're at it - it looks like nginx is only configured to use HTTP/1.1

dev-kraken added a commit to dev-kraken/next-self-host that referenced this issue Jan 7, 2025
- Implemented a cron job to automatically renew SSL certificates using Certbot.

Closes leerob#6
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

Successfully merging a pull request may close this issue.

1 participant