Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

owzo

Members
  • Joined

  • Last visited

  1. Hey everyone, I’m not sure if this is an issue on my end or something with the Docker image, but every time my server restarts, I’m forced to re-claim it again. The server doesn’t seem to retain the claim token or persistent auth data between restarts. I’ve confirmed my volumes are mapped, and nothing else seems out of the ordinary. Has anyone else run into this or know what might be causing it? Any suggestions would be appreciated! Thanks.
  2. Fixing Plex Behind Cloudflare Tunnel After the Latest Update Hey everyone! I’ve been running my Plex server behind a Cloudflare Tunnel for a while, but the recent Plex update introduced a change where the web interface now requires /web at the start of every request. Here’s how I fixed it with a simple URL Rewrite Rule in Cloudflare: Open Your Cloudflare Dashboard Log in to Cloudflare and select your account and website. Go to Rules > Overview. Click Create rule > URL Rewrite Rule. Configure the Rewrite Rule Rule Name: Plex Web UI Rewrite If Incoming Request matches: http*://plex.mydomain.com* Then… Action: Rewrite Path of Moved Section Target Path: (leave blank) Rewrite To: /web Your final rule should effectively read: Match requests to plex.mydomain.com/* and rewrite the path to /web. Save and Test Save the rule and make sure it’s enabled (you may need to drag it to the top of your rule list). Open your browser and visit: https://plex.mydomain.com You should be redirected automatically to /web and see the Plex login screen. Why This Works The Cloudflare Tunnel proxies requests from plex.mydomain.com to your local Plex server at localhost:32400. The URL Rewrite Rule appends /web to every incoming request, satisfying Plex’s new requirement without any extra bookmarks or manual redirects. That’s it! You’re back up and running. Hope this helps anyone else who ran into the same issue Cloudflare Tunnels! 😊
  3. Thank you so much, worked like a charm.
  4. Maybe this has already been asked, but is there a correct way to downgrade the qBittorrent-VPN to a pervious version? I accidentally updated my docker to 4.5, however my trackers have not whitelisted this version yet.
  5. I'm trying to create a new Instance of the binhex-plexpass docker but when i load the web UI it wont let me claim the server? It acts like its just in Client Mode and lets me access my other remote servers.
  6. I'm so happy to hear that it isn't just me. I was refreshing cookies, using different browsers, and i even check a different on computer with a vpn connation. Then I noticed our hero "TelefonSquid" chime in on this old thread.
  7. Should I look else ware for answer to my issue then?
  8. I don't know if I should be asking this question here or on the AMP forums but here it goes. I have 2 instances (Minecraft and Ark) up and running the the docker with out issues. I am currently working on getting a 3rd (Left 4 Dead 2) up and running. The instance installed perfectly, and the application updated fine as well. However when I try to start the server it self it bounces from having 0 memory to 23 and back again. A side note when I tried to start the server the first time after update it made me change the setting "Server IP Address - Which IP address the SRCDS server should listen on." from the loopback to eth0. Thanks for taking the time to read this. Edit - After about 2 hours it just crashed the instance. Edit 2 - This is all I found for log info [01:42:50] [API:admin Activity] : Starting the application. [01:42:52] [srcds:admin Warning] : The application stopped unexpectedly. Exit code 139 [01:42:54] [srcds:admin Warning] : The application stopped unexpectedly. Exit code 139 [01:42:55] [srcds:admin Warning] : The application stopped unexpectedly. Exit code 139
  9. Hi, I am currently trying to setup a new Influxdb docker on my new unraid 6.3.5 server. However when I attempt run the docker and access the admin web interface I am getting a connection refused. Can any one help with this issues? Let me know what information you would need from me to assist with this. Influxdb Container ID: 7970bf9a253a By: library/influxdb:latest up-to-date force update 8083/tcp 192.168.1.13:8083 8086/tcp 192.168.1.13:8086 /var/lib/influxdb /mnt/user/logs/ 8888888 .d888 888 8888888b. 888888b. 888 d88P" 888 888 "Y88b 888 "88b 888 888 888 888 888 888 .88P 888 88888b. 888888 888 888 888 888 888 888 888 8888888K. 888 888 "88b 888 888 888 888 Y8bd8P' 888 888 888 "Y88b 888 888 888 888 888 888 888 X88K 888 888 888 888 888 888 888 888 888 Y88b 888 .d8""8b. 888 .d88P 888 d88P 8888888 888 888 888 888 "Y88888 888 888 8888888P" 8888888P" [I] 2017-06-29T16:01:02Z InfluxDB starting, version 1.3.0, branch master, commit 76124df5c121e411e99807b9473a03eb785cd43b [I] 2017-06-29T16:01:02Z Go version go1.8.3, GOMAXPROCS set to 16 [I] 2017-06-29T16:01:02Z Using configuration at: /etc/influxdb/influxdb.conf [I] 2017-06-29T16:01:02Z Using data dir: /var/lib/influxdb/data service=store [I] 2017-06-29T16:01:02Z opened service service=subscriber [I] 2017-06-29T16:01:02Z Starting monitor system service=monitor [I] 2017-06-29T16:01:02Z 'build' registered for diagnostics monitoring service=monitor [I] 2017-06-29T16:01:02Z 'runtime' registered for diagnostics monitoring service=monitor [I] 2017-06-29T16:01:02Z 'network' registered for diagnostics monitoring service=monitor [I] 2017-06-29T16:01:02Z 'system' registered for diagnostics monitoring service=monitor [I] 2017-06-29T16:01:02Z Starting precreation service with check interval of 10m0s, advance period of 30m0s service=shard-precreation [I] 2017-06-29T16:01:02Z Starting snapshot service service=snapshot [I] 2017-06-29T16:01:02Z Starting continuous query service service=continuous_querier [I] 2017-06-29T16:01:02Z Starting HTTP service service=httpd [I] 2017-06-29T16:01:02Z Authentication enabled:false service=httpd [I] 2017-06-29T16:01:02Z Listening on HTTP:0.0.0.0:8086 service=httpd [I] 2017-06-29T16:01:02Z Starting retention policy enforcement service with check interval of 30m0s service=retention [I] 2017-06-29T16:01:02Z Listening for signals [I] 2017-06-29T16:01:02Z Sending usage statistics to usage.influxdata.com [I] 2017-06-29T16:01:02Z Storing statistics in database '_internal' retention policy 'monitor', at interval 10s service=monitor

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.