learnin2walk

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About learnin2walk

  • Rank
    Newbie

Recent Profile Visitors

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

  1. 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.
  2. 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.1
  3. 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;
  4. 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.
  5. 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
  6. Thank you for your response. Disabling the "documentserver_community" app allowed me to finish the upgrade to 18.0.6.
  7. Maintenance is set to 'false' on my config.php, yet I'm getting the screen below. Not sure how to get unstuck from this.
  8. 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:
  9. 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?
  10. 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) :
  11. Hello - I was wondering if there's a way to run this app on a subnet different than that of the unraid server? I know this is not the regular setup, but my home network is setup with VLANs for WIFI and LAN computers. When I set this up to run on the same VLAN as the unraid server (LAN) it works fine, but none of my WIFI clients can connect through it. Example: My LAN is 192.168.5.0/24. (unraid box and all LAN clients) My WIFI is 192.168.10.0/24. (all wifi clients) The unraid box is running on 192.168.5.9 and any LAN clients can use the proxy with no issues