EdgarWallace

Thanks a lot @saarg I just need one of these apps Collabora would be perfectly fine. I got the link from Collabora. AppImages does not run on Alpine which is the root cause that integrated Collabora app isn‘t running on Alpine Dockers....at least how I understood it.

I would kindly ask for advise: I was never successful in having the Collabora or Onlyoffice Docker running with my Nextcloud install and having read @saarg post is not giving big hope. The Collabora support replied on my question that I am getting an error message by accessing the build-in Collabora app: linuxserver.io Nextcloud docker is based on Alpine which uses musl libc instead of glibc - and AppImages do not work with musl libc: https://github.com/AppImage/AppImageKit/issues/1015 I would like to stick to my linuxserver.io Nextcloud install that is running rock solid since years rather than using another Nextcloud container. Is there a small chance that the issues will be resolved from your linuxserver.io side? Really, that is a question, NOT a complaint. Thank you.

Thanks a lot @ich777 Yes I indeed forwarded TCP and UDP and made the test. Results are attached, I do believe that this is looking fine? However, it takes ages, until someone is accepted to enter a TALK meeting. Did you made the same experience?

Hi, great work on the STUN-TURN-Server. Just asking for confirmation if I understood correct that I haver to open port 5349 in my router? And then adding myownnetwork.com:5349 into the STUN & TURN settings of Nextcloud/Settings/Talk? Thanks a lot.

@Menthalo I don't see that variable in my Docker settings. HAve you defined it yourself?

Thanks @aptalca. I am using a FritzBox as router and was searching that what you suggested and added myurl.com into the DNS-Rebind-Protection exception field and reebooted my router. Still no luck. Question remains, why it the error is coming up now.

Anyone else having an issue with the renewal of the certs? I am leaving the server switched on during the night and having looked at the "Troubleshooting Letsencrypt Image Port Mapping and Forwarding" guide and I can access my server via a cell phone as described in the troubleshooting guide. I haven't changed my router setting either (Ports 443 and 80 are forwarded since years...). Have no idea where to look next.

With the new Nextcloud version 18 I was hoping to enable and use the internal Onlyoffice but with the LSIO docker it seems to be an issue. I am back using your docker @Jidovu Marius Adrian I again performed all steps and have the docker running but currently only by adding https://192.168.178.28:4432/ into the Onlyoffice server address. As soon as I am trying to use https://myaddress.com/apps/onlyoffice I am getting this error: HealthcheckRequest on check error: Client error: `GET https://myaddress.com/apps/onlyoffice/healthcheck` resulted in a `401 Unauthorized` response: {"message":"Current user is not logged in"}

That is done. /mnt/user/system/docker/appdata/onlyoffice/DocumentServer/data is existing (however it is empty) but I created the /mnt/user/system/docker/appdata/onlyoffice/DocumentServer/data/certs folder which contains: -rwxr-xr-x 1 110 114 424 Dec 9 12:04 dhparam.pem* -rwxr-xr-x 1 110 114 1298 Dec 9 12:03 onlyoffice.crt* -rwxr-xr-x 1 110 114 1078 Dec 9 12:02 onlyoffice.csr* -rwxr-xr-x 1 110 114 1679 Dec 9 12:01 onlyoffice.key* I changes the template towards: https://[IP]:[PORT:4432] which is now successfully showing the Welcome Screen. Other than that no success. I will patiently waiting 🙂 Thank you very much!!

That doesn't work and I can't see any log messages. I have attached the setting of my container. http://192.168.178.28:8082/ is providing the welcome screen and the message, that onlyoffice is running https://192.168.178.28:4432/ is providing an error mesage - website not accessible http://server.com:8082/ is providing an error mesage - website not accessible https://server.com:4432/ is providing an error mesage - website not accessible

Yes - otherwise the demo server would not work I guess.

Sorry, in Nextcloud setting under onlyoffice you can try the demo server. I have installed Nextcloud and Let's Encrypt docker containers. Is there anything required regarding these settings?

Thanks a lot @Jidovu Marius Adrian for this docker. I was looking for a way to edit documents on my iPad without using MS Office/Word etc. Your guide is excellent and I was successfull installing the docker. Opening documents by using the demo server is working well. My only remaining issue is accessing my own server rather than the demo server. creating the onlyoffice network was successful http://192.168.178.28:8082/welcome/ ist showing: Document Server is running -rw-rw-rw- 1 root root 424 Dec 9 12:04 dhparam.pem -rw-rw-rw- 1 root root 1298 Dec 9 12:03 onlyoffice.crt -rw-rw-rw- 1 root root 1078 Dec 9 12:02 onlyoffice.csr -r-------- 1 root root 1679 Dec 9 12:01 onlyoffice.key https://192.168.178.28:4432/ isn't showing anything - just an error message There is only one error in the log: ==> /var/log/onlyoffice/documentserver/nginx.error.log <== but when I enter the container, the file is empty. Where should I look next? Thanks a lot.

I used the guide here to update my Nextcloud Docker: PSA: Nextcloud & CVE-2019-11043. Since then I am getting onyl an A security grade and some warnings: Der „X-Content-Type-Options“-HTTP-Header ist nicht so konfiguriert, dass er „nosniff“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der „X-Robots-Tag“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der „X-Download-Options“-HTTP-Header ist nicht so konfiguriert, dass er „noopen“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der „X-Permitted-Cross-Domain-Policies“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der "Referrer-Policy" HTTP-Header ist nicht gesetzt auf "no-referrer", "no-referrer-when-downgrade", "strict-origin", "strict-origin-when-cross-origin" oder "same-origin". Dadurch können Verweis-Informationen preisgegeben werden. Siehe die W3C-Empfehlung Seems that the "default" file for Nextcloud is ok as no one in the Nextcloud forum identified any issues with my file @saarg gave me the advise to check here if the "default" file of the Letsencrypt container could generate these warnings. All three "default" files are attached below. Thanks a lot for your help.

Well, @bastl, there is a section in /mnt/user/system/docker/appdata/letsencrypt/nginx/site-confs/default: ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; add_header X-Download-Options noopen; add_header X-Permitted-Cross-Domain-Policies none; add_header Referrer-Policy no-referrer always; However, all the settings are according to the requirements.

Yes - restarted after every change. Meanwhile I used the original configuration from the Nextcloud admin guide and adjusted server_name, root, ssl_certificate and ssl_certificate_key.....without any luck. Server is still giving warnings. Anyhow, I am going to use my "old" default file. Thanks a lot @bastl

Sure @bastl, it is basically what I posted above but please see below... The initial file is the "default" from a few posts above.

Thanks @bastl, however that was not the nessessary fix. I checked the admin manual 1000000 times (https://docs.nextcloud.com/server/16/admin_manual/installation/nginx.html) and still having no clue where the issue is sitting. @andreidelait, sure I am running 16.0.5 which is being provides by using the update channel "stable".

@saarg, I followed the guide that you posted so thanks a lot. After "default" was regenerated I discovered some security warnings (sorry for the German log but I do think that you know these messages :-)): Der „X-Content-Type-Options“-HTTP-Header ist nicht so konfiguriert, dass er „nosniff“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der „X-Robots-Tag“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der „X-Download-Options“-HTTP-Header ist nicht so konfiguriert, dass er „noopen“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der „X-Permitted-Cross-Domain-Policies“-HTTP-Header ist nicht so konfiguriert, dass er „none“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern. Der "Referrer-Policy" HTTP-Header ist nicht gesetzt auf "no-referrer", "no-referrer-when-downgrade", "strict-origin", "strict-origin-when-cross-origin" oder "same-origin". Dadurch können Verweis-Informationen preisgegeben werden. Siehe die W3C-Empfehlung.I don't get an A+ grade and no security warnings by using my "default" file. Have I done anything wrong and what's your advise moving forward? Thanks a lot.

Thanks @knex666 I was hoping that there was anything I overlooked so far. I am going to assign a second mariaDB docker to openHAB and will use br0 with a seperate IP address.

I received the "Urgent security issue in NGINX/php-fpm" recently. My setup runs rock solid since years now (I used this guide: https://blog.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/). 1.) Seems that the php package need to be updated and I am confident that this will happen via Docker update. 2.) Secondly two changes needed in the nginx config a.) the removal of $request_uri b.) the addition of the $try_files $fastcgi_script_name =404; 2b.) is done but I wasn't able to find 2a.). so seems that I am safe. Any further suggestions? Thanks a lot.

I was using a MariaDB Docker for the persistence services. The issue is, that I can't reach this database as it has the host IP. Any idea how to fix that? Thanks a lot.

Shame on me 😯 by accident I have installed KNX2 Binding and not KNX1 Binding that I need because I am still running KNX1. So sorry for having wasted your time please accept my apologize.

Sorry for the late reply....ping was not available, I had to install it into the container first: The openHAB 2.0 Network binding has limited use. The Docker Image does not have “ping” installed so the “use system ping” option cannot be set to true, and I could not find a way to give the Docker Container permission to bind to low numbered ports so the dhcp option doesn’t work. apt-get install iputils-ping Good news: the KNX/IP Gateways can be reached: root@4bdbe3f541db:/openhab# ping 192.168.178.1 PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data. 64 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=0.314 ms 64 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=0.303 ms openHAB Docker can be accessed from my Mac as well: PING 192.168.178.22 (192.168.178.22): 56 data bytes 64 bytes from 192.168.178.22: icmp_seq=0 ttl=64 time=0.632 ms 64 bytes from 192.168.178.22: icmp_seq=1 ttl=64 time=0.714 ms 64 bytes from 192.168.178.22: icmp_seq=2 ttl=64 time=0.668 ms

Hi, I can reach the Docker but it seems that the Docker can't reach the KNX/IP Gateway. Everything is on the same subnet (passing through the ZWave USB-stick is working fine). Extra Parameters: --device=/dev/ttyACM0 --shm-size 2g Network Type: Custom : br0 Fixed IP address (optional): 192.168.178.22 Subnet: 192.168.178.0/24, 2002:b0c7:a570::/64 The Ubuntu VM with openHAB is also defined with Network Bridge: br0 and all is working well (I don't have of course both VM and openHAB Docker not running in parallel).