vanzylp Posted August 8 Share Posted August 8 I recently had a hardware failure which resulted in ~80% new server components. Luckily (as expected) everything* came back once the array was attached and started. The only strange thing was that docker was disabled (not sure if this matters) once it was started up. Once docker was enabled, everything seemed to return to normal*. All but one container seems to be working properly. Nextcloud.... Setup: I have used Reverse Proxy based on SpaceInvaderONE's videos to access Nextcloud (Hosted domain --> Cloudflare --> DuckDNS --> SWAG). To my knowledge, everything was working prior to the hardware failure, but post-hardware failure, I am getting a 502 BAD GATEWAY error when I am attempting to access my server (nextcloud.mydomain.something) I corrected an issue in SWAG with the deprecated HTTP2 statement, and the log for SWAG now appears clean without any errors. The Nextcloud log on the other hand produces this error: ─────────────────────────────────────── Linuxserver.io version: 29.0.4-ls333 Build-date: 2024-08-06T11:50:55+00:00 ─────────────────────────────────────── using keys found in /config/keys **** The following active confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare the following files to the samples in the same folder and update them. **** **** Use the link at the top of the file to view the changelog. **** ┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐ │ old date │ new date │ path │ ├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤ │ 2022-08-20 │ 2023-08-13 │ /config/nginx/ssl.conf │ │ │ 2024-05-27 │ /config/nginx/nginx.conf │ │ 2023-04-13 │ 2024-06-24 │ /config/nginx/site-confs/default.conf │ └────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘ [custom-init] No custom files found, skipping... [ls.io-init] done. nginx: [emerg] no "events" section in configuration nginx: [emerg] no "events" section in configuration I tried adding the "events" line to the Nextcloud SWAG config file as shown below based on this poorly applicable post, to no avail. events {} #added to test error server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app 000.000.000.000; # edited for post set $upstream_port 000; # edited for post set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_hide_header X-Frame-Options; proxy_max_temp_file_size 2048m; } } At this point I am out of ideas on how to resolve this. Has anyone run into this and know how to resolve this? Quote Link to comment
JorgeB Posted August 8 Share Posted August 8 Please use the appropriate container support thread/Discord: Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.