EdgarWallace
-
Posts
894 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by EdgarWallace
-
-
I corrected according to your advise and the shutdown went fine yesterday. This should be visible from the diagnostics below. Cross fingers that the issue is gone.
Thanks again @dlandon
-
The is great advise @dlandon as I had several unclean shutdown's in the past weeks (when I tried to shutdown either via Main/Array Operation/PowerDown or via Dynamix System Buttons).
I followed your advise and have modified these settings:
- Settings->VM Manager->VM Shutdown time-out 300 seconds
- Settings->Disk Settings->Shutdown time-out 420 seconds
- Tips and Tweaks plugin: Processes to kill before Array is Stopped: ssh, bash
Here is the diagnostics from yesterday....I can't see that anything from the 3 new settings were preventing my array to shutdown but someone smarter than me might identify the root cause.
Thanks a lot.
-
On 9.4.2018 at 2:32 PM, aptalca said:
I'm guessing unraid keeps putting in the subdomains field because it is in the template? Then instead of deleting it, try setting it to either blank, or if that doesn't work set it to just a comma
Thank you very much @aptalca adding a comma into the subdomain(s) field is working well (adding a blank isn't working btw. this is what I tried earlier..)
@allanp81 you might want to try that as well. Let me know if it is working for you too.
-
Hi, I am having an issue with my Letsencrypt Docker whenever I am updating it. The log is showing: LOG
After each update I have to remove the Subdomain(s) but I am sure that there is a smarter way to deal with this. Anyone able to help?
Thanks a lot.
-
On 29.3.2018 at 11:51 AM, CHBMB said:
No, my guide and preferred method (more secure & less issues) is nextcloud.server.com
So have you fixed it then?
Sent from my LG-H815 using Tapatalk
I tried the method mentioned above but without any success.
-
Sure,
1 hour ago, CHBMB said:No, my guide and preferred method (more secure & less issues) is nextcloud.server.com
Sure, I double checked and am also using the nextcloud.server.com method.
Not fixed yet but I will try to tomorrow and reporting back if you think that is making sense.
-
I am running it as https://server.com/nextcloud which is your preferred setup - right?
I just discovered that there are some entries in /mnt/user/system/docker/appdata/nextcloud/nginx/site-confs/default which need some change:
rewrite ^/.well-known/carddav /remote.php/dav/ permanent; rewrite ^/.well-known/caldav /remote.php/dav/ permanent;
Should is rather look like:
rewrite ^/.well-known/caldav /nextcloud/remote.php/dav/ permanent; rewrite ^/.well-known/carddav /nextcloud/remote.php/dav/ permanent;
-
Thanks @CHBMB as always.
Do you have any great idea how to fix my issue? I can Imagine that I‘m not the only one....
-
I am having a sync issue on macOS which was also discussed here: Nextcloud: Calendar and Contacts with MacOS and iOS (iOS sync is working very well).
Seems that there is something needed in macOS: Troubleshooting Contacts & Calendar
The document is telling us that the
.htaccessfile has to be edited within the following lines to be added:Redirect301/.well-known/carddav/nextcloud/remote.php/Redirect301/.well-known/caldav/nextcloud/remote.php/dav
Which file do I have to choose as there are 2 of them:
- /mnt/user/system/docker/appdata/nextcloud/www/nextcloud/.htaccess
- /mnt/user/system/docker/appdata/nextcloud/www/nextcloud/config/.htaccess
Thanks for help.
-
4 hours ago, daemon9th said:
Hi,
I had the same issue with an Ubuntu 16.04 VM.
The interface I defined in /etc/network/interface had changed its name. Try "ip link show" command and then check configuration set in /etc/network/interfaces.
I just had to modify the name, and reload network service (or reboot).
Thanks to @bonienl for having looked into this however the fix that @daemon9th described worked for me. Thanks a lot!!!
-
The update from 6.4.1 went well, however my ubuntu VM lost it's network connection (see picture).
Any thoughts? Thanks a lot.
-
Update via WebUI went well. Running Nextcloud 13 now :-)
-
I have no clue if there is any other option but I do know that this was working well for me.
-
MinimWatch is available here, available for all kind of operating systems: LINK
I am running it on my macOS machine so that I am having full control over my music library.
-
Yes it was - I was not aware it's simply "allowed" to modify the unRAID's webui Port 443. I just changed it towards 442 and all is working again.
I do believe that some will fall into that trap as well as soon as they are updating. Maybe @aptalca you could add this to your great guide?
-
@CHBMB that means it‘s working for you under 6.4? I have altered my post and it shows that there is an issue with port 443 already assigned.
Gesendet von iPad mit Tapatalk -
The was doing the trick: port forward http (tcp 80 -->> 85) as well as https (tcp 443 -->> 443) is required.
This was working for unRAID 6.3.5 but it stopped working for 6.4.
Anyone Else whole made that experience? Latest letsencrypt Docker is installed:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e "EMAIL"="[email protected]" -e "URL"="mydomain.org" -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="4096" -e "PUID"="99" -e "PGID"="100" -e "HTTPVAL"="true" -p 85:80/tcp -p 443:443/tcp -v "/mnt/user/system/docker/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt68820e55413df4f6d12189d079334a943a01c4699136e38059fc459597f8670b/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (296916628be7ee045bd094ac8ebaa72631a8bd1146130c8480a19b91462dd0d4): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use.
Gesendet von iPad mit Tapatalk
-
@steve1977 have you checked the "Show Log" in MinimWatch which is available to control MinimServer? You have to accept Terms & Condition, otherwise MinimServer doesn't start.
-
Well, only with HOST option the server is showing up e.g. in KAZOO. And yes you need to add the ports as there is no template existing,.
-
I just changed the Repository towards: nielsdb97/docker-minimserver
This is a fork of the previous docker an is updated to the most recent version of MinimServer. All other Docker definitions can be kept.
-
1 hour ago, jasgud said:
applying this "fix" forces us to port forward http (tcp 80) through our router to access the nginx service so it can be evaluated by letsencrypt. Make sure you have http and https available externally.
The was doing the trick: port forward http (tcp 80 -->> 85) as well as https (tcp 443 -->> 443) is required.
Thanks a lot.
-
I applied the fix...still not working:
------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 4096 bit DH parameters present No subdomains defined E-mail address entered: [email protected] Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for xxxxxxxx.xxxxxx.org Waiting for verification... Cleaning up challenges Failed authorization procedure. xxxxxxxx.xxxxxx.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://xxxxxxxx.xxxxxx.org/.well-known/acme-challenge/igQwFM5uEZH-G1E1iS-R0v-GlcC3-xv-g9F1n-9r51g: Timeout IMPORTANT NOTES: - The following errors were reported by the server: Domain: xxxxxxxx.xxxxxx.org Type: connection Detail: Fetching http://xxxxxxxx.xxxxxx.org/.well-known/acme-challenge/igQwFM5uEZH-G1E1iS-R0v-GlcC3-xv-g9F1n-9r51g: Timeout To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. /var/run/s6/etc/cont-init.d/50-config: line 134: cd: /config/keys/letsencrypt: No such file or directory [cont-init.d] 50-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
-
Same here....everything was running fine until the todays container update:
------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 4096 bit DH parameters present No subdomains defined E-mail address entered: [email protected] Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. /var/run/s6/etc/cont-init.d/50-config: line 134: cd: /config/keys/letsencrypt: No such file or directory [cont-init.d] 50-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
-
Great that you sorted it out.
The remaining issue is that this Docker contains an old version of Minimserver so let‘s hope that this Docker is going to be updated.
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted · Edited by EdgarWallace
Since the last Nextcloud update (Nextcloud 13.0.2) it's complaining about some security issues I have added via my config settings:
However, the default file is showing the correct settings:
Anyone can guide me towards a solution? Thanks a lot.