H2O_King89
-
Posts
337 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by H2O_King89
-
-
If I go to https://requests.mydomain.com or http:// I get a refused connection/this site can't be reached. Now if I use https://192.168.1.10:1443 I get "your connection to this site isn't secure" due to not being able to validate certificate. So, this is progress! If I select to continue, I can then get "welcome to our server".
I guess a follow up here would also be how to be able to type in "requests.mydomain.com" and get https automatically? First need to figure out the certificate issue though.
Edit: made 2 changes in the container settings. Validation was changed from http to https, and AppData config path was changed from appdata/letsencrypt/config to just appdata/letsencrypt/ - I can now access ombi through https://requests.mydomain.com - now I need to find how to force https now so it doesn't have to be manually typed in.
Thank you for your patience and great wealth of knowledge, it's much appreciated.
For http to https its in the site config at the top. It say to remove the # for http to https.
Sent from my iPhone using Tapatalk Pro -
I'm starting to have a long boot time and it's stopping at this on logs
Non-interactive renewal: random delay of 380 secondsUpdate.. Todays update fix the long start up time.
-
Yes and yes, as per the video... Ed is really thorough about these things.
Like I said, I wanted to get at least Radarr and Sonarr working as I know Nextcloud can be a little more work.
Getting worried that my ISP (Rogers in Toronto, Canada) is blocking port 80, that would be a hell of a kick in the nuts!
So, the screenshots! [emoji4]
And, by the by, thanks for replying... it's appreciated!
If you get to server ready, ports shouldn’t be block. To check anyway you can go to canyouseeme and check your ports
Also if you haven’t setup http to https redirect you need to put https://
Sent from my iPhone using Tapatalk Pro
-
6 hours ago, bdosborn said:
I've got that warning too.
I can't remember if that was the error I got but I add this to the nextcloud.subdomain.config
add_header Referrer-Policy no-referrer always; -
On 9/25/2018 at 8:43 PM, Dazog said:
it's now out of bata
-
@Roppy84
Can you get to it by plex.tv? Did you change in plex setting>network>Secure connections to "Required"?
Sent from my iPhone using Tapatalk Pro -
@roppy84
Post your docker template dockers>plex>edit
Sent from my iPhone using Tapatalk Pro -
As I had already mentioned I had tried that already without success - Still same issue - Plex not reachable from local network.
Anyone ? Ideas/Solutions?
So you tried host and still can’t get to the GUI?
Why limit the template to a host-only network?
Or rather, may I submit a request to have the Ports populated in the NetworkSettings?
They probably set it up this way so it works right out of the box.
Here looks like a list of ports
Sent from my iPhone using Tapatalk Pro -
Thank you for posting this.
I am having the identical error and was going to do the screenshots, but yours is exactly it.
I noticed in the Docker Image the Exposed Ports are defined properly, but
NetworkSettings: Ports: {}, are empty.
I believe this is the cause of the issue.
It’s because the template is setup for host so no port needs map. If it gets changed to a different network then the port needs map so it is pass.
Sent from my iPhone using Tapatalk Pro -
Yeah i am. I dont know much since im new to the whole area but i thought about the proxy being the problem but it’s the first problem in almost a year with no change. How do I determine if its the proxy or not?
Turn proxy off on radarr and see if it fixes the issue.
If it does it’s the proxy that’s the issue.
Sent from my iPhone using Tapatalk Pro -
1: Yes
2: Yes
3: Yes
4: Yes
5: Only thing that changed was i updated the docker which i’ve done mant times before
Are you using a proxy?
Sent from my iPhone using Tapatalk Pro -
Change plex back to host
In the proxy config change proxy pass upstream:32400
To ip:32400
Sent from my iPhone using Tapatalk Pro -
It's definitely been fixed now, probably an issue with your locally cached template
Sent from my Mi A1 using Tapatalk
First time installing it. Adding the m fix it
Sent from my iPhone using Tapatalk Pro -
On 9/22/2018 at 7:26 PM, saarg said:
I thought we fixed that a long time ago... Apparently we didn't.
just tried for the first time also and same issue
-
how do I setup a password?
I tired editing the settings.js removing the // and putting my password in. but when I try logging in it doesn't take
tried making admin node with no luck
$ npm install -g --unsafe-perm node-red-admin npm WARN deprecated [email protected]: bcrypt < v2.0.0 is susceptible to bcrypt wrap-around bug. Upgrade to bcrypt >= v2.0.0 for improved support for newer bcrypt hashes npm WARN deprecated [email protected]: Use uuid module instead npm WARN deprecated [email protected]: The major version is no longer supported. Please update to 4.x or newer npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules npm ERR! path /usr/local/lib/node_modules npm ERR! code EACCES npm ERR! errno -13 npm ERR! syscall access npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules' npm ERR! { Error: EACCES: permission denied, access '/usr/local/lib/node_modules' npm ERR! stack: 'Error: EACCES: permission denied, access \'/usr/local/lib/node_modules\'', npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'access', npm ERR! path: '/usr/local/lib/node_modules' } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator (though this is not recommended). npm ERR! A complete log of this run can be found in: npm ERR! /usr/src/node-red/.npm/_logs/2018-10-01T02_24_50_639Z-debug.log -
I followed [/url] guide to setting up reverse proxies and letsencrypt and wanted to get this to work for me with plex. I do the following:
- Create a CNAME for my domain called 'plex', so should be able to access plex through 'plex.mydomain.com' (not my real domain obviously)
- Put my duckdns domain + token into the DuckDNS container settings
- Setup port forwarding as described in the spaceinvaderone video (80 -> 180, 443 -> 1443)
- Setup a user defined network 'proxynet'
- Run letsencrypt using 'proxynet'
- Install linuxserver.io's plex container and make it use the 'proxynet' network
- Check that the plex.subdomain.conf file is set up correctly, shown below
# make sure that your dns has a cname set for plex, if plex is running in bridge mode, the below config should w$g the IP$address of plex# replace the line "proxy_pass https://$upstream_plex:32400;" with "proxy_pass https://HOSTIP:32400;" HOSTIP bei$.yourdom$in.url:443")# in plex server settings, under network, fill in "Custom server access URLs" with your domain (ie. "https://ple$server { listen 443 ssl; server_name plex.*; include /config/nginx/ssl.conf; client_max_body_size 0; proxy_redirect off; proxy_buffering off;# enable for ldap auth, fill in ldap details in ldap.conf#include /config/nginx/ldap.conf; location / {# enable the next two lines for http auth#auth_basic "Restricted";#auth_basic_user_file /config/nginx/.htpasswd;# enable the next two lines for ldap auth#auth_request /auth;#error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s;set $upstream_plex plex; proxy_pass https://$upstream_plex:32400; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier; proxy_set_header X-Plex-Device $http_x_plex_device; Text proxy_set_header X-Plex-Device-Name $http_x_plex_device_name; Text proxy_set_header X-Plex-Platform $http_x_plex_platform; proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version; proxy_set_header X-Plex-Product $http_x_plex_product; proxy_set_header X-Plex-Token $http_x_plex_token; proxy_set_header X-Plex-Version $http_x_plex_version; proxy_set_header X-Plex-Nocache $http_x_plex_nocache; proxy_set_header X-Plex-Provides $http_x_plex_provides; proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor; proxy_set_header X-Plex-Model $http_x_plex_model;}}This should be posted in LE Topic.
-
I got the containers port mapped to the host and it connects to the web_ui. However I'm not sure why I keep getting a bad gateway error trying to connect with https://plex.spikedevelopments.com
I take it you are trying to proxy? Probably should use the help topic. But I’ll I’ll give it a go. Post your proxy config for plex. I bet you didn’t put the ip of the server in.
Sent from my iPhone using Tapatalk Pro -
Has the problem of listening on multiple interfaces been fixed?
Just curious
Sent from my BND-L34 using Tapatalk
What is the issue this is causing? I tried looking and couldn’t find
Sent from my iPhone using Tapatalk Pro -
36 minutes ago, TomH said:
It seems that it is only my DVD movies (ripped to VOB-files) that are not working. TS, mkw, mpg, m4v is working. Wmv files too.
Anyone know how to find and change the codec for VOB-files ?
I could transcode all movies with Handbrake but it will take ages...
I installed binhex to test and came with 1.13.5.5332 and it works.
I rolled back linux docker to 1.13.5.5332 and doesn't work.
im going to try and nuke linux config and try from new
linux pulled 1.13.8.5395 with a new config. my media is loading but was able to play a truehd now.
-
On 9/21/2018 at 3:28 PM, TomH said:
I got the same problem now. My Plex has been working well for months but now the Plex docker has stop transcode. I got one movie to work but I think it was a mpeg-4 file.
im having issue transcode also.
-
is there an issue with mounted drives for upload?
I try sending files to my google:secure folder and sends a few files then getting errors
found this in the logs
WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes -
1 minute ago, ken-ji said:
This is weird. Other than the proxynet bridge, did you create any other bridges by cli?
because the bridges in your network interfaces (from the diags) named br-* do not line up with those the docker is reporting... only docker networks of type bridge can be seen with the ifconfig -a
Maybe @bonienl has some idea...
just that proxy net and have reboot with no issues for months then reboot a few days ago and started having this issue and found this topic.
-
root@KING-UNRAID:~# docker network list NETWORK ID NAME DRIVER SCOPE 9494a8ea6aac br0 macvlan local 2b4bf512628e bridge bridge local e8e134764a20 host host local 27a6395f1007 none null local 0dd83d63baea proxynet bridge local -
11 minutes ago, ken-ji said:
Post you diagnostics file. I'm guessing there's something wrong in your config that's causing the docker to treat the br0 network as a custom definition and possibly purging it. You might also want to provide the screenshot of your docker network settings 'Settings | Docker'
king-unraid-diagnostics-20180918-1703.zip
[Support] binhex - qBittorrentVPN
in Docker Containers
Posted · Edited by H2O_King89
Is there extraction for rar?
Also I got this working as a subdomain with nginx
proxy_pass http://ip:port; 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-Proto $scheme; proxy_hide_header Referer; proxy_hide_header Origin; proxy_set_header Referer ''; proxy_set_header Origin ''; } }