SgtSeamonkey

For anyone looking for answers I followed exactly what georgebrooksmso posted above HOWEVER I used "image: odoo:17.0" after struggling with V15 from CA. I could never get V15 from CA to work with NGINX reverse proxy, V17.0 works fine with the proxy conf below (odoo.subdomain.conf) server { listen 80; listen 443 ssl; listen [::]:443 ssl; server_name odoo.*; 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_odoo [IPADDRESSOFYOURSERVER]; proxy_pass http://$upstream_odoo:8069; } location ~* /web/static/ { #proxy_cache_valid 200 60m; #proxy_buffering on; #expires 864000; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_odoo [IPADDRESSOFYOURSERVER]; proxy_pass http://$upstream_odoo:8069; } } I have not and likely will not look into the conversion of a V15 database to V16/17. I'll likely re-enter my data. If you want to test V17 without risking your current data I recommend changing your "Database Storage Path" in the postgresql:15 image to something different (e.g. I changed mine from /mnt/cache/appdata/postgresql15 to /mnt/cache/appdata/postgresql15test). This will create a new folder without destroying your old data and let you create and test a new DB, then you can switch back to the original path to work on a conversion.

Where are the web files stored? I am looking to upload files, it says I have to use Uploadcare and add a script to the HTML head. However there is no folder for Officelife in my Appdata folder. Is it possible to upload files locally or use local files instead of Uploadcare?

Well, the issue is now resolved and I don't think it was an issue with my VPN, I think it was a Plex issue. Upon returning home I had the same issue until I updated PlexPass to the latest version. After that I was able to see and claim my server. It was still a little finicky, I jumped back and forth between plex.tv and the local address webpages. Refreshing and logging in a few times. Eventually I was able to claim the server and everything is now back to normal. I did not have to change any settings.

Totally identical. No different than using the direct address over VPN.

Alright, I'm back with another issue and it's certainly a misunderstanding on my part that has caused it. My ISP recently changed my IP address and I didn't recognize it - I thought I was hacked therefore I changed my Plex password and force logged-out all devices. I also updated to the latest Plex version. Logging in seemed to work with the new password so I looked no deeper and went out of town on a business trip. Now I'm sitting in the hotel room trying to connect and unable to. I assumed I had to disconnect and re-claim my server so I logged into my VPN - I now have full access to my local network but I see no options to claim my server - though it didn't put up any fuss when I removed the existing server connection. Maybe I am misunderstanding how Open VPN works - I have full access to my local 192.168 network at home: My server, my router, etc. but when I go to http://192.168.xxx.xxx:32400/web/index.html I see no options beyond the generic ones. It's as if it doesn't recognize that I am indeed on that local network and cannot see my plex server. I suspect this is the case as I also cannot access any share folders through windows explorer - if I click on my pinned shortcuts it says "the local device name is already in use" and if I hard type \\192.168.xxx.xxx or \\192.168.xxx.xxx\ShareFolderName it asks for a username and password and then either claims I do not have access or that the username/password combination is wrong.

Yeah, I tried general support first and got no response. My initial thought was hardware, possibly power draw or thermals but I couldn't find any issues. I will look into the full diagnostic dump. Thank you for the response! Update 1/28/21 - Looks like the issue was the power supply. Haven't tested extensively but during initial testing after upgrading PSU I have not yet seen the issue.

I've been inconsistently crashing while watching movies through Plex. I'm not sure the extent of the crash, I lose connection to my server, run downstairs to check it and it's still powered on. By the time I return upstairs the connection is restored but the array is stopped. Happens inconsistently. I watched multiple episodes of a TV show in a row multiple nights in a row without issue. Sometimes I can watch an entire movie, other times I can only watch minutes. Turned on Syslog mirror to flash but I'm not sure what to look for, nothing is standing out. I recently upgraded my Unraid server from an i3-8100 to an i9-9900k to help with movie transcoding in Plex. I did not upgrade my motherboard hardware, which is an ASRock H370M-ITX/ac Mini ITX, I did however upgrade my BIOS to the latest. This is the only issue since the upgrade and I had no issues before that. Has anyone else run into this? Versions: Unraid 6.8.3, Docker 19.03.5, tried the latest Plex and Plexpass dockers.

Is that for the subdomain issue? I keep getting a 502 Bad Gateway error - none of my other subdomains are having an issue. Although I did have to change port 8118 to 8119 (which I may have done incorrectly) since 8118 is being used by deluge. I have both deluge and qbittorrent because the deluge version isn't whitelisted by a private tracker I use. When I search "iptable" in supervisord.log I see many instances of this: With the only differences between them being the timestamps and the "4" and "8" on lines 4 & 5.

I just added this docker today and was able to get it up and running. Was on the WebUI (via 192.168.1.69:8080) without issue, but wasn't able to connect, and still can't, from my subdomain (qbittorrent.WEBSITE.com). In my troubleshooting I went into the QBitTorrent Options -> WebUI and turned on the WebUI and set the IP address and port to match my Unraid QBitTorrent docker. After this I immediately lost connection to the WebUI and have not been able to get it back. I imagine setting the WebUI in the QBitTorrent options to match the Docker caused a conflict, but now I'm not sure how to resolve this issue. Edit: I solved this issue by going to \\tower\appdata\binhex-qbittorrentvpn\qBittorrent\config and editing the qBittorrent.conf file. At the bottom you'll see a section for WebUI -- at first I tried to just wipe the "WebUI\Address" to "*" but that didn't work. So I deleted the entire WebUI section. It reverted the password back to the default so I had to go change it again, but it got me back onto the WebUI.