learnin2walk

Members
  • Posts

    16
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

learnin2walk's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Apologies for reviving an old thread, but I'm trying to get this going and I'm getting a "bad healthcheck status" error when trying to connect to my onlyoffice DS. I can get to the server's welcome screen from a web browser, but when I try to connect to it in nextcloud the error below appears. I'm using nginx proxy manager This is the error: Exception: Bad healthcheck status /config/www/nextcloud/apps/onlyoffice/controller/settingscontroller.php - line 172: OCA\Onlyoffice\DocumentService->checkDocServiceUrl() /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 218: OCA\Onlyoffice\Controller\SettingsController->SaveAddress() /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 127: OC\AppFramework\Http\Dispatcher->executeController() /config/www/nextcloud/lib/private/AppFramework/App.php - line 157: OC\AppFramework\Http\Dispatcher->dispatch() /config/www/nextcloud/lib/private/Route/Router.php - line 302: OC\AppFramework\App::main() /config/www/nextcloud/lib/base.php - line 993: OC\Route\Router->match() /config/www/nextcloud/index.php - line 37: OC::handleRequest() What is the URL you guys are using within nextcloud to connect to ONLYOFFICE? I just use my full domain name like documentserver.mydomain.com
  2. I also went with this combo. I'm interested in using the iGPU with a windows 10 VM. Is this possible? Do I need a second/dummy card? @Hoopster any advise on this?
  3. Any idea why a subdomain would start throwing 502 gateway errors after it has been working for months? My ApacheGuacamole docker. I can no longer connect to it from outside my network. Getting 502 error. If I try the internal IP it works fine. No changes in UNRAID or docker configs. It just stopped working. I've restarted both containers. Everything was working correctly. Setup with Letsencrypt and cloudflare. I have 8 other proxyhosts with no issues setup the same way. ApacheGuac is setup with custom:br0 interface with separate IP than unraid server Any ideas would be appreciated.
  4. Yes, I'm using a custom bridge. I've changed the name to all lowercase but it still shows 400 bad request error. I also tried changing the port in the proxy_pass line to match the port mapped in the container (4430) but that gave me a 502 gateway error message. Are there any logs we can look at to see what's going on? edit: I looked at the nginx log and it shows this message: 2020/12/18 07:34:27 [error] 469#469: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.5.1, server: opendoc.*, request: "GET / HTTP/2.0", upstream: "https://172.19.0.2:4430/", host: "opendoc.mydomain.com" 2020/12/18 07:34:27 [error] 469#469: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.5.1, server: opendoc.*, request: "GET /favicon.ico HTTP/2.0", upstream: "https://172.19.0.2:4430/favicon.ico", host: "opendoc.mydomain.com", referrer: "https://opendoc.mydomain.com/"
  5. Sorry, I ended up figuring it out. Cox blocks incoming port 80, so the http validation would not work. I switched to dns + cloudflare to bypass that. The only problem I have now is with the onlyoffice container not working via the domain. It works fine with the internal unraid_ip:port, but I get a "400 bad request" error if using the domain name. I'm using the proxy conf file from spaceinvader's video, which I'm attaching. Is there something wrong that jumps out? # only office doc server server { listen 443 ssl; server_name opendoc.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_docs OnlyOfficeDocumentServer; proxy_pass https://$upstream_docs:443; proxy_redirect off; 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-Host $server_name; proxy_set_header X-Forwarded-Proto $scheme; } }
  6. I did, thanks. I enabled cloudflare dns validation and was able to get past the errors, but still can't access my apps. This is what the ngnix log shows: 192.168.5.1 is my pfsense box. Anything else that I could check? Like I said, I have not made any change in my pfsense or unraid config. I have rebooted both just in case to no avail. 2020/12/16 15:08:49 [error] 472#472: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.5.1, server: cloud.*, request: "GET / HTTP/2.0", upstream: "https://172.19.0.4:1443/", host: "cloud.mydomain.com" 2020/12/16 15:08:50 [error] 472#472: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.5.1, server: cloud.*, request: "GET /favicon.ico HTTP/2.0", upstream: "https://172.19.0.4:1443/favicon.ico", host: "cloud.mydomain.com", referrer: "https://cloud.mydomain.com/"
  7. Hello - As of last night, my swag/letsencrypt container can't retrieve new certs. It's getting stuck in the challenge phase and reporting it might be a firewall issue. I've not made any changes to my firewall (pfsense) and I can see the traffic passing from the WAN to the unRaid box (see logs below). I've tried removing and re-adding the container to no avail. I also verified my DNS and CNAME records are correct and resolve to my IP via duckdns. I changed my actual domain name to mydomain.com in the logs for privacy. Please assist. I've attached below the logs from swag and also a screenshot of my firewall log showing the traffic passing through. Let me know if any other logs would help. Thank you. ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- 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... Variables set: PUID=99 PGID=100 TZ=America/Chicago URL=mydomain.com SUBDOMAINS=cloud,docsrv,bw1,cctv EXTRA_DOMAINS= ONLY_SUBDOMAINS=true VALIDATION=http DNSPLUGIN= EMAIL=director@mydomain.com STAGING=false SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d cloud.mydomain.com -d docsrv.mydomain.com -d bw1.mydomain.com -d cctv.mydomain.com E-mail address entered: director@mydomain.com http validation is selected Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Account registered. Requesting a certificate for cloud.mydomain.com and 3 more domains Performing the following challenges: http-01 challenge for bw1.mydomain.com http-01 challenge for cctv.mydomain.com http-01 challenge for cloud.mydomain.com http-01 challenge for docsrv.mydomain.com Waiting for verification... Challenge failed for domain cctv.mydomain.com Challenge failed for domain cloud.mydomain.com Challenge failed for domain docsrv.mydomain.com Challenge failed for domain bw1.mydomain.com http-01 challenge for cctv.mydomain.com http-01 challenge for cloud.mydomain.com http-01 challenge for docsrv.mydomain.com http-01 challenge for bw1.mydomain.com Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: cctv.mydomain.com Type: connection Detail: Fetching http://cctv.mydomain.com/.well-known/acme-challenge/axPVzX1R_0b-z_RUA4RFpx49MHuuuNahNC_j91SaWqI: Timeout during connect (likely firewall problem) Domain: cloud.mydomain.com Type: connection Detail: Fetching http://cloud.mydomain.com/.well-known/acme-challenge/U45bVQqmdevLwK7wKy0AbDomXOzoZgLvqYXYgRzxld0: Timeout during connect (likely firewall problem) Domain: docsrv.mydomain.com Type: connection Detail: Fetching http://docsrv.mydomain.com/.well-known/acme-challenge/YgPNqYJs7Vm9eBME8emyeRH50UR4qpMlfjmkCtmPNjo: Timeout during connect (likely firewall problem) Domain: bw1.mydomain.com Type: connection Detail: Fetching http://bw1.mydomain.com/.well-known/acme-challenge/udN7LtCgSavk48_JkuoDJ6VUMaNXx3_AtP3g95NnWM8: Timeout during connect (likely firewall problem) 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. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
  8. Thank you for your response. Disabling the "documentserver_community" app allowed me to finish the upgrade to 18.0.6.
  9. Maintenance is set to 'false' on my config.php, yet I'm getting the screen below. Not sure how to get unstuck from this.
  10. Hello - I've been running this container together with Onlyoffice Document Server and it's been working great. Today I tried to upgrade nextcloud from 18.0.4 to 18.0.6 and I'm getting the error below. Not sure how to proceed from here. My nextcloud instance is now stuck in the upgrade phase. Please advise. 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 2020-06-09T13:18:51+00:00 Set log level to debug 2020-06-09T13:18:51+00:00 Turned on maintenance mode 2020-06-09T13:18:51+00:00 Repair step: Repair MySQL collation 2020-06-09T13:18:51+00:00 Repair info: All tables already have the correct collation -> nothing to do 2020-06-09T13:18:51+00:00 Repair step: Repair SQLite autoincrement 2020-06-09T13:18:51+00:00 Repair step: Copy data from accounts table when migrating from ownCloud 2020-06-09T13:18:51+00:00 Repair step: Drop account terms table when migrating from ownCloud 2020-06-09T13:18:51+00:00 Updating database schema 2020-06-09T13:18:51+00:00 Updated database 2020-06-09T13:18:51+00:00 Updating <documentserver_community> ... 2020-06-09T13:18:52+00:00 Repair step: Rebuild font library 2020-06-09T13:18:52+00:00 Exception: sh: ../../tools/allfontsgen: not found 2020-06-09T13:18:52+00:00 Update failed 2020-06-09T13:18:52+00:00 Maintenance mode is kept active 2020-06-09T13:18:52+00:00 Reset log level Keep maintenance mode active? [y/N] n 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 Maintenance mode disabled
  11. Sorry for the noob question, but will the container get updated with 17.0.2 eventually, or do we have to update from within Nextcloud and then run the commands above?
  12. Hello - i've been using this container for a while and just recently started having a problem. It seems that I can no longer get metadata for TV Shows. Movies work fine. Looking at the logs, I see a lot of these: 2019-11-16 23:52:19,761 (14ec6e274700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)> 2019-11-16 23:52:19,765 (14ec6f77e700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)> 2019-11-16 23:52:19,766 (14ec6e274700) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/81189-7.jpg' 2019-11-16 23:52:19,768 (14ec6e073700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)> 2019-11-16 23:52:19,769 (14ec6f77e700) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/81189-11.jpg' 2019-11-16 23:52:19,773 (14ec6e073700) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/81189-9.jpg' 2019-11-16 23:52:19,787 (14ec6e475700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)> 2019-11-16 23:52:19,790 (14ec6e475700) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/81189-17.jpg' 2019-11-16 23:52:19,848 (14ec6f77e700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)> 2019-11-16 23:52:19,848 (14ec6e274700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)> I did some googling and this thread https://forums.plex.tv/t/https-broken/216635/18 in Plex forums mentioned that SSL was broken within Plex. I don't understand why this recently stopped working. I thought it was my database, so I deleted all of it, and re-added all libraries but same problem. I have also tried other Plex containers and have the same issue. Any ideas?