Fix webserver Pi port to 80 in nginx example configs

Co-authored-by: Junie <junie@jetbrains.com>
This commit is contained in:
2026-07-24 15:56:03 +02:00
co-authored by Junie
parent 1ffe884eba
commit fd31f02091
3 changed files with 17 additions and 5 deletions
+13 -1
View File
@@ -357,6 +357,18 @@
**AI Response**: "Updated `nginx/reverse-proxy-nginx.conf.example` (test) to use `test.slpsoftware.nl` as `server_name`, with an HTTP server block for the Let's Encrypt ACME challenge + redirect to HTTPS, and an HTTPS server block referencing certbot-managed certificate paths (`/etc/letsencrypt/live/test.slpsoftware.nl/...`) — matching the user's existing certbot/Let's Encrypt workflow on the reverse-proxy Pi, which terminates SSL before forwarding plain HTTP to the webserver Pi. Added a new `nginx/reverse-proxy-nginx-production.conf.example` documenting the future production reverse-proxy config for `slpsoftware.nl`/`www.slpsoftware.nl` (not yet wired up, since production deploy automation is still an open item). Updated `deployment-plan.md` and `deployment-instructions.md` with the domain/DNS/certbot setup steps for both environments."
**Context**: Post-workflow follow-up (feature already marked Complete); addresses the user's feedback that domain name and SSL certificate handling should have been clarified during the earlier deployment follow-up. Changes not yet committed/pushed.
**Context**: Post-workflow follow-up (feature already marked Complete); addresses the user's feedback that domain name and SSL certificate handling should have been clarified during the earlier deployment follow-up. Changes committed on `feature/updates_gitea_workflow` (commit `1ffe884`).
---
## Post-Completion Follow-up: Webserver Port Corrected to 80
**Timestamp**: 2026-07-24T15:54:00Z
**User Input**: "Ik leid al het verkeer door naar poort 80 op de webserver pi (Pi Main)"
**AI Response**: "Corrected the assumed internal port for the webserver Pi: updated `nginx/webserver-nginx.conf.example` (`listen 192.168.1.103:80` / `listen [::]:80`) and `nginx/reverse-proxy-nginx.conf.example` (`proxy_pass http://192.168.1.103:80`), replacing the previously assumed port `8080`. No other files referenced this port."
**Context**: Post-workflow follow-up (feature already marked Complete); corrects an incorrect assumption from the earlier test-environment deploy follow-up. Changes not yet committed/pushed.
---
@@ -1,6 +1,6 @@
# Voorbeeldconfiguratie voor de nginx reverse proxy op de andere Raspberry Pi
# (degene die wél vanaf het internet bereikbaar is en het binnenkomende verkeer
# doorstuurt naar de webserver-Pi op 192.168.1.103:8080) — voor de TESTOMGEVING,
# doorstuurt naar de webserver-Pi op 192.168.1.103:80) — voor de TESTOMGEVING,
# bereikbaar via het domein test.slpsoftware.nl.
#
# Kopieer dit bestand handmatig naar bijvoorbeeld
@@ -46,7 +46,7 @@ server {
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
location / {
proxy_pass http://192.168.1.103:8080;
proxy_pass http://192.168.1.103:80;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
@@ -12,8 +12,8 @@
server {
# Alleen luisteren op het interne (LAN) IP-adres van deze Pi, niet op 0.0.0.0,
# zodat deze poort niet per ongeluk vanaf buiten het netwerk bereikbaar is.
listen 192.168.1.103:8080;
listen [::]:8080;
listen 192.168.1.103:80;
listen [::]:80;
server_name _;