Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

Nefertiti · 29. Oktober 2021

old one is

## Version 2021/10/26 - Changelog: https://github.com/linuxserver…/root/defaults/proxy.conf

# Timeout if the real server is dead

proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

# Proxy Connection Settings

proxy_buffers 32 4k;

proxy_connect_timeout 240;

proxy_headers_hash_bucket_size 128;

proxy_headers_hash_max_size 1024;

proxy_http_version 1.1;

proxy_read_timeout 240;

proxy_redirect http:// $scheme://;

proxy_send_timeout 240;

# Proxy Cache and Cookie Settings

proxy_cache_bypass $cookie_session;

#proxy_cookie_path / "/; Secure"; # enable at your own risk, may break certain apps

proxy_no_cache $cookie_session;

# Proxy Header Settings

proxy_set_header Connection $connection_upgrade;

proxy_set_header Early-Data $ssl_early_data;

proxy_set_header Host $host;

proxy_set_header Proxy "";

proxy_set_header Upgrade $http_upgrade;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header X-Forwarded-Host $host;

proxy_set_header X-Forwarded-Proto https;

proxy_set_header X-Forwarded-Ssl on;

proxy_set_header X-Real-IP $remote_addr;

_______________

new one is

## Version 2021/10/26 - Changelog: https://github.com/linuxserver…/root/defaults/proxy.conf

# Timeout if the real server is dead

proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

# Proxy Connection Settings

proxy_buffers 32 4k;

proxy_connect_timeout 240;

proxy_headers_hash_bucket_size 128;

proxy_headers_hash_max_size 1024;

proxy_http_version 1.1;

proxy_read_timeout 240;

proxy_redirect http:// $scheme://;

proxy_send_timeout 240;

# Proxy Cache and Cookie Settings

proxy_cache_bypass $cookie_session;

#proxy_cookie_path / "/; Secure"; # enable at your own risk, may break certain apps

proxy_no_cache $cookie_session;

# Proxy Header Settings

proxy_set_header Connection $connection_upgrade;

proxy_set_header Early-Data $ssl_early_data;

proxy_set_header Host $host;

proxy_set_header Proxy "";

proxy_set_header Upgrade $http_upgrade;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header X-Forwarded-Host $host;

proxy_set_header X-Forwarded-Proto https;

proxy_set_header X-Forwarded-Ssl on;

proxy_set_header X-Real-IP $remote_addr;

Code

root@fc9b4c690308:/#/config/nginx/proxy.conf

[/EDIT]
bash: /config/nginx/proxy.conf: Permission denied
bash: [/EDIT]: No such file or directory
root@fc9b4c690308:/#^C
root@fc9b4c690308:/#

so far working only with the old one

Soma · 29. Oktober 2021

Zitat von Nefertiti

so far working only with

The 2 files you posted are the same, 😉

The zip file you posted before had the old version.

If it's OK now, great.

Nefertiti · 29. Oktober 2021

Well my mistake yes it is working but only with the old file The second one (2019)

Code

## Version 2021/10/26 - Changelog: https://github.com/linuxserver/docker-swag/commits/master/root/defaults/proxy.conf

# Timeout if the real server is dead
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

# Proxy Connection Settings
proxy_buffers 32 4k;
proxy_connect_timeout 240;
proxy_headers_hash_bucket_size 128;
proxy_headers_hash_max_size 1024;
proxy_http_version 1.1;
proxy_read_timeout 240;
proxy_redirect  http://  $scheme://;
proxy_send_timeout 240;

# Proxy Cache and Cookie Settings
proxy_cache_bypass $cookie_session;
#proxy_cookie_path / "/; Secure"; # enable at your own risk, may break certain apps
proxy_no_cache $cookie_session;

# Proxy Header Settings
proxy_set_header Connection $connection_upgrade;
proxy_set_header Early-Data $ssl_early_data;
proxy_set_header Host $host;
proxy_set_header Proxy "";
proxy_set_header Upgrade $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Forwarded-Ssl on;
proxy_set_header X-Real-IP $remote_addr;

Alles anzeigen

Code

## Version 2019/10/23 - Changelog: https://github.com/linuxserver/docker-letsencrypt/commits/master/root/defaults/proxy.conf

client_body_buffer_size 128k;

#Timeout if the real server is dead
proxy_next_upstream error timeout invalid_header http_500 http_502 http_503;

# Advanced Proxy Config
send_timeout 5m;
proxy_read_timeout 240;
proxy_send_timeout 240;
proxy_connect_timeout 240;

# TLS 1.3 early data
proxy_set_header Early-Data $ssl_early_data;

# Basic Proxy Config
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Ssl on;
proxy_redirect  http://  $scheme://;
proxy_http_version 1.1;
proxy_set_header Connection "";
#proxy_cookie_path / "/; HTTPOnly; Secure"; # enable at your own risk, may break certain apps
proxy_cache_bypass $cookie_session;
proxy_no_cache $cookie_session;
proxy_buffers 32 4k;
proxy_headers_hash_bucket_size 128;
proxy_headers_hash_max_size 1024;

Alles anzeigen

Soma · 29. Oktober 2021

Zitat von Nefertiti

Well my mistake yes it is working but only with the old file The second one (2019)

That makes no sense, the file is for the deceased letsencrypt, not swag.

What swag version are you running?

Nefertiti · 29. Oktober 2021

Code

build_version    Linuxserver.io version:- 1.11.0-ls157 Build-date:- 2021-01-05T19:21:19+00:00
maintainer    aptalca
org.opencontainers.image.authors    linuxserver.io
org.opencontainers.image.created    2021-05-13T01:49:59-04:00
org.opencontainers.image.description    SWAG - Secure Web Application Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php support and a built-in certbot client that automates free SSL server certificate generation and renewal processes (Let's Encrypt and ZeroSSL). It also contains fail2ban for intrusion prevention.
org.opencontainers.image.documentation    https://docs.linuxserver.io/images/docker-swag
org.opencontainers.image.licenses    GPL-3.0-only
org.opencontainers.image.ref.name    c48705cbc49216b4e0f1679863ea265cf83d5176
org.opencontainers.image.revision    c48705cbc49216b4e0f1679863ea265cf83d5176
org.opencontainers.image.source    https://github.com/linuxserver/docker-swag
org.opencontainers.image.title    Swag
org.opencontainers.image.url    https://github.com/linuxserver/docker-swag/packages
org.opencontainers.image.vendor    linuxserver.io
org.opencontainers.image.version    1.15.0-ls57

Alles anzeigen

Nefertiti · 29. Oktober 2021

yes before I was using letsencrypt and updated to the latest Swag but did not change anything in directory nginx

Nefertiti · 30. Oktober 2021

Nevermind I just recreated the whole thing in a new directory by making a new volume name

/srv/dev-disk-by-uuid-2e5438fd-633f-4658-82b0-dce4dccd3b97/AppData/Config/letsencrypt

I changed it to

/srv/dev-disk-by-uuid-2e5438fd-633f-4658-82b0-dce4dccd3b97/AppData/Config/swag

And I copy paste my old proxy-confs directory

everything is ok

Sorry for the trouble

KM0201 · 30. Oktober 2021

Good lord..lol.

What instructions are you following to install Nextcloud? Obviously you're trying to set up a reverse proxy.. are you doing this with a domain you've purchased or duckdns or what?

There's so much crazy in all that I'd suggest starting over... Really Nextcloud should be up and running, w/ a reverse proxy, in less than 30min, easy.

Nefertiti · 30. Oktober 2021

Actually I use to have nectcloud at that time no issue but for now I do not have any use of it so I even do not have the container on my new server but of course I am using swag for my other container and I ran into this

Code

Just a remark (and reminder, especially for those that run WatchTower or any other updater):


SWAG latest (Release 1.20.0-ls94) comes with an important safety update.

If you only update the image, the file in question (proxy.conf) won't be updated.


In order to update the file, you'll have to delete the old one and redeploy SWAG to download the latest version of it.

from Soma since I was following the thread so the Issue was I went a long time ago from letsencrypt to swag and keeping the old directories because I did not want to loose my old custom proxy-confs, everything did work until I try to update today

everything is fixed since it was not properly installed in first place

KM0201 · 1. November 2021

Zitat von Nefertiti
Actually I use to have nectcloud at that time no issue but for now I do not have any use of it so I even do not have the container on my new server but of course I am using swag for my other container and I ran into this
Code
Just a remark (and reminder, especially for those that run WatchTower or any other updater):


SWAG latest (Release 1.20.0-ls94) comes with an important safety update.

If you only update the image, the file in question (proxy.conf) won't be updated.


In order to update the file, you'll have to delete the old one and redeploy SWAG to download the latest version of it.
from Soma since I was following the thread so the Issue was I went a long time ago from letsencrypt to swag and keeping the old directories because I did not want to loose my old custom proxy-confs, everything did work until I try to update today
everything is fixed since it was not properly installed in first place

Gotcha. LE has been deprecated for quite some time, so I guess that didn't really dawn on me.

Glad you got it worked out.

chente · 12. November 2021

NEW NEXTCLOUD UPDATE.

Version 22.2.1. https://nextcloud.com/blog/kee…-23rc1-is-here-help-test/

Remember to update from the application itself. Open the notifications and follow the instructions.

KM0201 · 12. November 2021

Zitat von chente

NEW NEXTCLOUD UPDATE.
Version 22.2.1. https://nextcloud.com/blog/kee…-23rc1-is-here-help-test/
Remember to update from the application itself. Open the notifications and follow the instructions.

If you don't want to use the GUI updater... run the following as root or as a user w/ docker privileges... (I'd already ran it this morning but it goes through the same steps, making a backup, etc.)

Code

ken@openmediavault:~$ docker exec -it nextcloud updater.phar
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4

Current version is 22.2.1.

No update available.

Nothing to do.
ken@openmediavault:~$

chente · 13. November 2021

NEXTCLOUD FIXES UPDATE FROM YESTERDAY, NEW VERSION TODAY 22.2.2

If you installed version 22.2.1 yesterday, you must upgrade to version 22.2.2 released today. Fixed a bug that degraded performance.

https://nextcloud.com/changelog/

https://github.com/nextcloud/server/pull/29682

Remember to update from within the app, don't update the docker.

Agricola · 13. November 2021

This is why I like to wait a week or two to update container services: let somebody else discover the bugs.

KM0201 · 13. November 2021

Zitat von chente

NEXTCLOUD FIXES UPDATE FROM YESTERDAY, NEW VERSION TODAY 22.2.2
If you installed version 22.2.1 yesterday, you must upgrade to version 22.2.2 released today. Fixed a bug that degraded performance.
https://nextcloud.com/changelog/
https://github.com/nextcloud/server/pull/29682
Remember to update from within the app, don't update the docker.

So why do you say update in the app, and not within docker? It pulls the exact same update and follows the exact same procedure. I've had problems with the GUI updater crashing in the past (granted it has been a while), thus why I usually run it at the command line..

Code

ken@openmediavault:~$ docker exec -it nextcloud updater.phar
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4

Current version is 22.2.1.

Update to Nextcloud 22.2.2 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-22.2.2.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[✔] Downloading
[✔] Verify integrity
[✔] Extracting
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
[✔] Done

Update of code successful.

Should the "occ upgrade" command be executed? [Y/n] y
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
2021-11-13T18:37:51+00:00 Setting log level to debug
2021-11-13T18:37:51+00:00 Repair step: Repair MySQL collation
2021-11-13T18:37:52+00:00 Repair info: All tables already have the correct collation -> nothing to do
2021-11-13T18:37:52+00:00 Repair step: Repair SQLite autoincrement
2021-11-13T18:37:52+00:00 Repair step: Copy data from accounts table when migrating from ownCloud
2021-11-13T18:37:52+00:00 Repair step: Drop account terms table when migrating from ownCloud
2021-11-13T18:37:52+00:00 Updating database schema
2021-11-13T18:37:52+00:00 Updated database
2021-11-13T18:37:52+00:00 Checking for update of app accessibility in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "accessibility" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app activity in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "activity" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app bruteforcesettings in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "bruteforcesettings" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app circles in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "circles" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app cloud_federation_api in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "cloud_federation_api" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app comments in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "comments" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app contactsinteraction in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "contactsinteraction" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app dashboard in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "dashboard" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app dav in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "dav" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app federatedfilesharing in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "federatedfilesharing" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app federation in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "federation" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app files in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "files" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app files_pdfviewer in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "files_pdfviewer" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app files_rightclick in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "files_rightclick" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app files_sharing in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "files_sharing" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app files_trashbin in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "files_trashbin" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app files_versions in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "files_versions" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app files_videoplayer in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "files_videoplayer" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app firstrunwizard in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "firstrunwizard" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app logreader in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "logreader" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app lookup_server_connector in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "lookup_server_connector" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app nextcloud_announcements in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "nextcloud_announcements" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app notifications in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "notifications" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app oauth2 in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "oauth2" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app password_policy in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "password_policy" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app photos in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "photos" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app privacy in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "privacy" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app provisioning_api in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "provisioning_api" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app serverinfo in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "serverinfo" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app settings in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "settings" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app sharebymail in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "sharebymail" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app sharingpath in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "sharingpath" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app support in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "support" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app survey_client in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "survey_client" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app systemtags in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "systemtags" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app text in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "text" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app theming in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "theming" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app twofactor_backupcodes in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "twofactor_backupcodes" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app unsplash in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "unsplash" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app updatenotification in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "updatenotification" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app user_status in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "user_status" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app viewer in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "viewer" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app weather_status in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "weather_status" in App Store 
2021-11-13T18:37:54+00:00 Checking for update of app workflowengine in appstore
2021-11-13T18:37:54+00:00 Checked for update of app "workflowengine" in App Store 
2021-11-13T18:37:55+00:00 Repair step: Repair MySQL collation
2021-11-13T18:37:55+00:00 Repair info: All tables already have the correct collation -> nothing to do
2021-11-13T18:37:55+00:00 Repair step: Repair mime types
2021-11-13T18:37:55+00:00 Repair step: Clean tags and favorites
2021-11-13T18:37:55+00:00 Repair info: 0 tags of deleted users have been removed.
2021-11-13T18:37:55+00:00 Repair info: 0 tags for delete files have been removed.
2021-11-13T18:37:55+00:00 Repair info: 0 tag entries for deleted tags have been removed.
2021-11-13T18:37:55+00:00 Repair info: 0 tags with no entries have been removed.
2021-11-13T18:37:55+00:00 Repair step: Repair invalid shares
2021-11-13T18:37:55+00:00 Repair step: Move .step file of updater to backup location
2021-11-13T18:37:55+00:00 Repair info: .step file exists
2021-11-13T18:37:55+00:00 Repair info: .step-previous-update removed
2021-11-13T18:37:55+00:00 Repair info: .step file moved to .step-previous-update
2021-11-13T18:37:55+00:00 Repair step: Add move avatar background job
2021-11-13T18:37:55+00:00 Repair info: Repair step already executed
2021-11-13T18:37:55+00:00 Repair step: Add preview cleanup background jobs
2021-11-13T18:37:55+00:00 Repair step: Fix potential broken mount points
2021-11-13T18:37:55+00:00 Repair info: No mounts updated
2021-11-13T18:37:55+00:00 Repair step: Repair language codes
2021-11-13T18:37:55+00:00 Repair step: Install new core bundle components
2021-11-13T18:37:55+00:00 Repair step: Add log rotate job
2021-11-13T18:37:55+00:00 Repair step: Clear frontend caches
2021-11-13T18:37:55+00:00 Repair info: Image cache cleared
2021-11-13T18:37:55+00:00 Repair info: SCSS cache cleared
2021-11-13T18:37:55+00:00 Repair info: JS cache cleared
2021-11-13T18:37:55+00:00 Repair step: Clear every generated avatar on major updates
2021-11-13T18:37:55+00:00 Repair step: Add preview background cleanup job
2021-11-13T18:37:55+00:00 Repair step: Queue a one-time job to cleanup old backups of the updater
2021-11-13T18:37:56+00:00 Repair step: Cleanup invalid photocache files for carddav
2021-11-13T18:37:56+00:00 Repair step: Add background job to cleanup login flow v2 tokens
2021-11-13T18:37:56+00:00 Repair step: Remove potentially over exposing share links
2021-11-13T18:37:56+00:00 Repair info: No need to remove link shares.
2021-11-13T18:37:56+00:00 Repair step: Clear access cache of projects
2021-11-13T18:37:56+00:00 Repair step: Reset generated avatar flag
2021-11-13T18:37:56+00:00 Repair step: Keep legacy encryption enabled
2021-11-13T18:37:56+00:00 Repair step: Check encryption key format
2021-11-13T18:37:56+00:00 Repair step: Remove old dashboard app config data
2021-11-13T18:37:56+00:00 Repair step: Add job to cleanup the bruteforce entries
2021-11-13T18:37:56+00:00 Repair step: Queue a one-time job to check for user uploaded certificates
2021-11-13T18:37:56+00:00 Repair step: Repair DAV shares
2021-11-13T18:37:56+00:00 Repair step: Add background job to set the lookup server share state for users
2021-11-13T18:37:56+00:00 Starting code integrity check...
2021-11-13T18:38:00+00:00 Finished code integrity check
2021-11-13T18:38:00+00:00 Update successful
2021-11-13T18:38:00+00:00 Maintenance mode is kept active
2021-11-13T18:38:00+00:00 Resetting log level

Keep maintenance mode active? [y/N] n
ken@openmediavault:~$

Alles anzeigen

KM0201 · 13. November 2021

Zitat von Agricola

This is why I like to wait a week or two to update container services: let somebody else discover the bugs.

That's certainly good practice. I've generally found with a lot of heavily used, OS software.. legitimate bugs that slip through beta testing, affect a small number of users with some unique situations... same with OMV. I really can't recall votdev pushing a OMV release from beta to to stable, and there was a serious bug that affected a majority of users. Now with my OS (whether it's Debian, Ubuntu, Mint.. )... I usually wait till the first point release... but even when I've been an early adopter.. I've generally found serious bugs that weren't fixed quickly were pretty rare.

I'd only accessed NC once after updating (and that was right after the update).. so I hadn't noticed any problem with it.

chente · 13. November 2021

Zitat von KM0201

So why do you say update in the app, and not within docker?

I'm not saying "don't update from docker". I say "don't update the Docker".

I understand that the application update can be done in the GUI within the application or in the CLI within the application. The result will be the same, as you said.

What I'm saying is don't update the full package in portainer or docker.

Sorry if my English is not perfect. You know I translate with google. I correct some things but ...

chente · 13. November 2021

Zitat von chente

Sorry if my English is not perfect. You know I translate with google. I correct some things but ...

I have an advocate with this issue Re: openmediavault-flushmailq

Starbuck1973 · 30. November 2021

Well, some months later. I tried again, now following:

RE: Nextcloud Bad Gateway

Ports forwarded (internal 443/80, ext 444/80). I checked are open

I connected to the duckdns url outside of my network to avoid any loopback issue.

On step 11, I got the screen "Welcome to your SWAG instance". Is it correct?

I continued the tutorial, I didn't find major issues till the step 22. When I connect I got "502 Bad Gateway nginx"

I tried also to change the file nextcloud.subdomain.conf following the instructions of

Let's Encrypt > NextCloud reverse proxy issues (Bad Gateway / host not found)

I replaced this

Code

#        set $upstream_app nextcloud;
#        set $upstream_port 443;

with

Code

set $upstream_app 192.168.35.24;
set $upstream_port 444;
set $upstream_proto https;

proxy_pass $upstream_proto://$upstream_app:$upstream_port;

Then swag was restarted, but problem persists

How can I solve it?

Thanks in advance!

KM0201 · 1. Dezember 2021

Zitat von Starbuck1973
Well, some months later. I tried again, now following:
RE: Nextcloud Bad Gateway
Ports forwarded (internal 443/80, ext 444/80). I checked are open

I connected to the duckdns url outside of my network to avoid any loopback issue.
On step 11, I got the screen "Welcome to your SWAG instance". Is it correct?

I continued the tutorial, I didn't find major issues till the step 22. When I connect I got "502 Bad Gateway nginx"

I tried also to change the file nextcloud.subdomain.conf following the instructions of
Let's Encrypt > NextCloud reverse proxy issues (Bad Gateway / host not found)
I replaced this
Code
#        set $upstream_app nextcloud;
#        set $upstream_port 443;
with
Code
set $upstream_app 192.168.35.24;
set $upstream_port 444;
set $upstream_proto https;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

Then swag was restarted, but problem persists

How can I solve it?

Thanks in advance!
Alles anzeigen

Is the swag screen secured w/ SSL? That post walks you through everything. You shouldn't need to change anything else to have it working with Duckdns.

I said very clearly in that post, not to combine it with other tutorials. It walks you through completely what you need to do.

Also..

Zitat

Ports forwarded (internal 443/80, ext 444/80). I checked are open

That should be 443/80 to 444/81... 443/80 should be external, 444/81 internal

Jetzt mitmachen!