tooviral
-
Posts
63 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by tooviral
-
-
Have a cache pool of 4 devices in raid 0 I believe and will be upgrading board and cpu soon.
I have a 2tb nvme that id like to replace those 4 drives with.
Do I change it to raid 1 and then add the 2tb and let it balance, then remove one by one and rebalance between each pull?
Just not sure best way to go about it.
-
Had a disk report some errors.
Parity returned no errors as it scheduled run started just after these errors popped up.
I've ran an extended self test and it completed without error.
Don't think its cables as this is in a supermicro 24 bay system and hasn't moved
Will prob order a replacement soon.
-
Hello,
Tryin to repair the database and not sure how to stop plexmediaserver in the docker img.
Tried "service plexmediaserver stop" doesn't work
Any ideas?
-
Its reported as closed still.
Noticed another container variable "ADDITIONAL_PORTS" in logs and tried adding the incoming port and still no joy.
Latest start logs attached.
-
8 hours ago, binhex said:
it wont set the incoming port for you automatically, the only provider that i support automatic incoming port assignment is PIA, all others you need to manually assign the port using your vpn providers web portal and then set the port in the app.
Ive done that in rtorrent.rc and added the variable -e 'VPN_INCOMING_PORT'='12528' and it still shows a closed in rutorrent and https://portchecker.co/
-
So I've noticed in the logs this
2020-09-26 08:02:04,415 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignmentIt looks like its not setting the port forward. Could this be my problem?
-
Seems it may have been a fluke as I am now getting the red exclamation mark too.
My docker start command is as follows
Quoteroot@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-rtorrentvpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXX' -e 'VPN_PASS'='XXXX' -e 'VPN_REMOTE'='ca-tor-002.mullvad.net' -e 'VPN_PORT'='1198' -e 'VPN_PROTOCOL'='udp' -e 'VPN_INCOMING_PORT'='12528' -e 'VPN_DEVICE_TYPE'='tun' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRONG_CERTS'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'ENABLE_FLOOD'='no' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='192.168.1.1,8.8.8.8,8.8.4.4' -e 'DEBUG'='false' -e 'PHP_TZ'='UTC' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'WEBUI_PASS'='XXXX' -e 'RPC2_PASS'='XXXX' -p '3001:3000/tcp' -p '5000:5000/tcp' -p '9080:9080/tcp' -p '9443:9443/tcp' -p '8119:8118/tcp' -v '/mnt/cache/downloads/':'/data':'rw' -v '/mnt/cache/appdata/binhex-rtorrentvpn':'/config':'rw' --log-opt max-size=50m --log-opt max-file=1 'binhex/arch-rtorrentvpn'
Am I doing something wrong?
-
didnt make any changes to the files, added user/pass to docker variable and put these files in the openvpn folder
-
On 9/16/2020 at 8:33 PM, cardo said:
Can you provide more information about how you configured the container/router, because I set this up 4-5 days ago and it is still failing for me.
Here were my steps:
1. Set up the port forward on Mullvad.
2. set up a port forwarding rule on my router from anywhere to my private IP and port I’ve set up on Mullvad. It is set for both TCP/UDP.3. Created two port entries in the container, one for UDP and one for TCP and specified the port on Mullvad and my router’s port forward rule.
4. Edited the .torrent.rc file and specified the port like this: network.port_range.set = xxxx-xxxx where xxxx is the port number.5. When starting the container and going to Settings > Connection > Port used for income connection shows my port. Yet the status still shows the exclamation mark with the port being closed.
All I did was
1. Set up the port forward on Mullvad.
2. Edited the .torrent.rc file and specified the port like this: network.port_range.set = xxxx-xxxx where xxxx is the port number and set "network.port_random.set = no"
and worked
-
12 hours ago, cheesemarathon said:
Has anyone managed to get port forwarding working with Mullvad? I have the VPN connection working but rtorrent reports the port is closed.
It may take some time for it to show open, took a day or two for me.
-
On 9/9/2020 at 5:58 AM, binhex said:
So where does that leave us?, well not quite up sh*t creek without a paddle :-), you can set 'STRICT_PORT_FORWARDING' to 'no' and this will then allow you to connect to any legacy endpoint, however this will mean you wont have a working incoming port so speeds will be lower than usual - its not ideal i know, but its the best we have got right now until PIA sort their sh*t out (not happy).
its 'STRICT_PORT_FORWARD' for the variable
wasnt working and was using this reference instead of the faq you have
Always refer to the faq lol
-
Tring to install on a new machine and getting xml error
-
Just did a preclear with the preclear plugin
-
Bought a couple of these about 6 months ago and shucked them for the bare drives which were ST8000DM004 models.
They are both now starting to show read errors.
Just a warning to others.
-
So it seems a Hikvision surveillance camera that is on the same network was somehow hijacking the portforwad. Removed from network and the container is now running as it was.
Thanks to @CHBMB for troubleshooting with me.
-
I thought so too, but latest version do it automatically
-
Yes, was working fine before. Upgraded to 6.4 and noticed shortly thereafter it wasn't working. Had it running on 81 and 444 before. Changed it to its own ip with 80 and 443 and nada.
Not sure why the reg nginx works, but not letsencrypt.
-
port forwarding, like i said its working fine on port 80 with nginx alone
-
dynamic dns with freedns.afraid.org
I've also started the reg nginx container and am able to pull up a test html with same port forwards. So its not the forwarding.
-
I have, logs, run command and my port forwarding
I've also started the reg nginx container and am able to pull up a test html with same port forwars.
-
As I've said I've read through all relevant post that have been highlighted and nothing is working.
Running the nginx docker only and I'm able to pull up a test html.
-
So I've read through the last couple of pages and do not know why I am getting this error
------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- 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... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.*************.ca -d plexrequests.*************.ca -d sonarr.*************.ca -d sab.*************.ca -d rtorrent.*************.ca -d plexpy.*************.ca -d radarr.*************.ca -d anime.*************.ca E-mail address entered: [email protected] Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for *************.ca http-01 challenge for www.*************.ca http-01 challenge for plexrequests.*************.ca http-01 challenge for sonarr.*************.ca http-01 challenge for sab.*************.ca http-01 challenge for rtorrent.*************.ca http-01 challenge for plexpy.*************.ca http-01 challenge for radarr.*************.ca http-01 challenge for anime.*************.ca Waiting for verification... Cleaning up challenges IMPORTANT NOTES: uthorization procedure. www.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.*************.ca/.well-known/acme-challenge/57SSLSGnDQA25SGGYykkYxXH6PcNeZ0a8XOM4sOPNMs: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", *************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://*************.ca/.well-known/acme-challenge/QmV4FybwAmGud_U1cBtrmTioIG3bEcoFdaZ1vmbK700: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", rtorrent.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://rtorrent.*************.ca/.well-known/acme-challenge/8cUEPZ3biWP1LZMXy945qaLn_IkudgI74kvZ26hR4rs: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", sonarr.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://sonarr.*************.ca/.well-known/acme-challenge/Q7CnOK-6C3PRw0ZLHyEPWJ8E0b-tFX5dKHhNF4k4MOs: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", radarr.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://radarr.*************.ca/.well-known/acme-challenge/yyHOUYplvYz1PZTqyL7hg27eLC6b-e0zBx6nnZTm3kY: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", plexpy.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://plexpy.*************.ca/.well-known/acme-challenge/nsW1rxfch2W9_JEPgTqip-TjZUjD0518ES3ytsgTMI0: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", anime.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://anime.*************.ca/.well-known/acme-challenge/xa65wZrMCuCe6dW27LZJ8Blt4MVji5fyenl7kez5Kk4: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", plexrequests.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://plexrequests.*************.ca/.well-known/acme-challenge/-vx6US77kC7-uneuYZBwYTqCZXQ7EB_mZGAPjRWh32Q: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>", sab.*************.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://sab.*************.ca/.well-known/acme-challenge/J2cx-gPUi3v-4DBrr1hZpeZBOc2WSf7wy3vP7H8c594: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" - The following errors were reported by the server: Domain: www.*************.ca Type: unauthorized Detail: Invalid response from http://www.*************.ca/.well-known/acme-challenge/57SSLSGnDQA25SGGYykkYxXH6PcNeZ0a8XOM4sOPNMs: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: *************.ca Type: unauthorized Detail: Invalid response from http://*************.ca/.well-known/acme-challenge/QmV4FybwAmGud_U1cBtrmTioIG3bEcoFdaZ1vmbK700: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: rtorrent.*************.ca Type: unauthorized Detail: Invalid response from http://rtorrent.*************.ca/.well-known/acme-challenge/8cUEPZ3biWP1LZMXy945qaLn_IkudgI74kvZ26hR4rs: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: sonarr.*************.ca Type: unauthorized Detail: Invalid response from http://sonarr.*************.ca/.well-known/acme-challenge/Q7CnOK-6C3PRw0ZLHyEPWJ8E0b-tFX5dKHhNF4k4MOs: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: radarr.*************.ca Type: unauthorized Detail: Invalid response from http://radarr.*************.ca/.well-known/acme-challenge/yyHOUYplvYz1PZTqyL7hg27eLC6b-e0zBx6nnZTm3kY: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: plexpy.*************.ca Type: unauthorized Detail: Invalid response from http://plexpy.*************.ca/.well-known/acme-challenge/nsW1rxfch2W9_JEPgTqip-TjZUjD0518ES3ytsgTMI0: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: anime.*************.ca Type: unauthorized Detail: Invalid response from http://anime.*************.ca/.well-known/acme-challenge/xa65wZrMCuCe6dW27LZJ8Blt4MVji5fyenl7kez5Kk4: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: plexrequests.*************.ca Type: unauthorized Detail: Invalid response from http://plexrequests.*************.ca/.well-known/acme-challenge/-vx6US77kC7-uneuYZBwYTqCZXQ7EB_mZGAPjRWh32Q: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" Domain: sab.*************.ca Type: unauthorized Detail: Invalid response from http://sab.*************.ca/.well-known/acme-challenge/J2cx-gPUi3v-4DBrr1hZpeZBOc2WSf7wy3vP7H8c594: "<!DOCTYPE html> <html><head><title>Document Error: Not Found</title></head> <body><h2>Access Error: 404 -- Not Found</h2> <p>" 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. 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
Docker run command
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="br0" --ip="192.168.1.30" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -e "TCP_PORT_80"="80" -e "TCP_PORT_443"="443" -e "EMAIL"="************" -e "URL"="*****.ca" -e "SUBDOMAINS"="www,plexrequests,sonarr,sab,rtorrent,plexpy,radarr,anime" -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="2048" -e "PUID"="99" -e "PGID"="100" -e "HTTPVAL"="true" -v "/mnt/cache/appdata/letsencrypt":"/config":rw --log-opt max-size=50m --log-opt max-file=1 linuxserver/letsencrypt 7b8965d3de4fbf31cf00b4c1da227ce94fa4cb05b60abf008c91ae61e88e8616 The command finished successfully!Port 80 and 443 are forwarded to 192.168.1.30 on my EdgeRouter Lite.
Any help appreciated
-
-
On 10/14/2017 at 11:33 AM, tooviral said:
Any way to prevent this from happening. This has been the second time I've had to do a balance.
Any ideas?
Cache upgrade
in General Support
Posted
thx Jorge