DioxideC

Ive set everything up as suggested in the faq, added 8080 to vpn outputs, the *arrs to vpn inputs and tried multiple combinations to test. I can access the UIs no problem and they connect through the vpn ip no problem, But the *arrs just cant communicate with sab and keep timing out. I cant work out why. Ive tried with priv enabled and disabled from the sab config, ive tried with proxy ticked and unticked in the settings of the *arr UIs. No difference. Very stumped here. Edit: Realised that the default lan network needed changing in the sabnzbvpn config all working now

No, as far as I can tell no it does not. After entering your UnRaid IP into the ignored field after testing that they connect to sab successfully I then open up a console from the Sonar/Radar docker containers and using this command $ curl ifconfig.io reveals your public ip address. Sab is still behind the proxy tho. UPDATE - This worked for Radarr only, when I tried adding the ports for Sonarr my sab container failed and radarr and sonarr got stuck in a constant rebuild loop, my sab container turned into an orphan image, I resolved this by re installing the docker image for sabnzbvpn and re added all the settings, ports etc started working apart from connecting to sab Ive worked it out. The steps I have taken are: 1. For Radarr, unticked use proxy in the general settings. 2. Followed steps from A24 from posted doc https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md 3. Made sure that the port was added under ADDITIONAL_PORTS as well as adding the port using the add another path, port...etc (so it appears twice in the config) 4. Using the add another path, port etc selected config type variable under key create VPN_OUTPUT_PORTS with the vpn container port number which would be your sabnzb port as the value. Then create another variable type of VPN_INPUT_PORTS with value as the port number of the application you want to access so Radarrs default web ui port. 4. Made sure the vpn container starts first. 5. Tested using curl ifconfig.io on console. Also you can only access the ui by typing in ip:port in address bar as no webui link will appear in Unraid anymore. 6. Make sure to check your LAN_NETWORK ip range. it might of reverted back to default and need updating. All working now same applies to any of the *arrs

Thanks for the reply Ive tried "disable_startup_check: true" but seems to come up with the same errors. Ill try a few more things then ill re do it all over from the start. I have 1 more question. How else are people editing their config files?, because of the permissions I cant edit it within app data, All I can do is edit a file on my machine then copy over the file using the config edit app plugin. Which is also most annoying. Edit: 10/12/20 - 02:00am: Mananged to get it working by starting the config conf file from scratch, might of been a space somewhere it should of been but not 100% either way started up the container got to the UI, tried to log in using the display name and password I set in the users_database.yml and It states incorrect username and password with this error in the log: Getting closer to having it working but im getting blocked at every turn lol. Any ideas? examples of my config and users database file for ref: Edit:10/12/20 10:16am ok so after doing some more fine checking, changed the users yml to this: also made sure that database_index: 0 was included. Now when I try and log in it doesnt seem to throw any errors but doesn't redirect away from the login screen. I think I read others were having that issue in this thread so will go back and read up. After doing some reading I went ahead to the next step with NPM, got my ssl for the domain with lets encrypt fine, added in the info but when going to the domain i get an error to many redirects? Firefox gives me this: any ideas? Update: 12:41pm after much hair pulling, googling, reading, shooting scrubs on Arma 3. I found out that the ssl/tls settings on cloudflare were the cause of indefinite redirect issues. I can now also log in but am unable to set up the second factor part, I now get this error: To Overcome this error I continued on as mentioned in an earlier post. I also had to make sure that my container name was changed from binhex-jellyfin to just jellyfin in the protected endpoint config. now to set up smtp as it trys to send the 2fa setup process via email. Finally we are getting there Edit: 11/12/20 13:07: Ok so all seems to be working well locally. Now getting a 403 forbidden error when an external ip tries to access example.domain.co.uk. the address bar changes to > https://example.domain.co.uk/?rd=http://example.domain.co.uk/ and gives the 403 error. if you manually put an s in making it now > https://example.domain.co.uk/?rd=https://example.domain.co.uk/ it works after that. I read a user a few posts back had this issue couldnt find any fixes for this yet tho? My settings for NPM are http for my endpoint, and even changing to https doesnt make a difference it still comes up as > https://example.domain.co.uk/?rd=http://example.domain.co.uk/ and gives the 403 error. That ?rd= needs to convert to https but not sure how or where it does that part yet. any ideas?

Could a mod maybe move this to the docker support section if relevant?

Can anyone shed some light on this? Otherwise I think ill have to start again from scratch. Heres what ive done/noticed so far: 1. Copied your config and pasted over the one created and continued to follow the instructions. 2. At this part I wasn't sure if I had to literally type in 'YOURPASSWORD' or replace it with one of the 128bit keys or a normal txt password, So i used a 128b key. 3. When trying to start up I keep getting these errors which seem to relate to smtp which I do not have setup yet?: 4. Commented out smtp part of the config and set up txt file for notifications, tried true and false for notification check made no difference. 5. Line 324 in my config doesn't reference a key so not sure what's going on? I'm sure its just something stupid I've done, but any help is appreciated otherwise I will delete it all and start over.

Hi, I want to be able to assign a hostname to some of my containers and access them from lan using http://jellyfin, http://ombi for example. I have tried adding --hostname jellyfin to the extra parameter field and -h jellyfin. But neither of those seem to work. I also tried docker run --hostname jellyfin in the extra params field but the container would not start stating an error such as "lookup docker on 192.168.66.1:53: no such host" I have searched the forums already and found no adequate answers. I wonder if you kind folks could help me and tell me where im going wrong and what exactly I need to do to get this working? Someone here must have this setup with hostnames? Thanks.