2 hours ago, Kuddel said:

edit: added docker.txt from diagnostics.zip

I asked because I wanted to see how your shares are configured and if there are any other errors in your syslog.

The full diagnostics would be very helpful.

Thank you very much for your help. I think I found the mistake thanks to your suggestions. Some time ago, I moved some Docker remnants from the RAID to the SSD. Apparently, I forgot to adjust a path in the Docker. Due to the update and the associated new data, or data in 'wrong' locations, this caused the problems. I think I've been able to correct it now.

 

I'm new to Unraid, setting up some docker containers....

I installed the OpenVPN-Client container and looks like it working now, I installed the Firefox container to test and it reports the VPN IP address.

Is there a way to test if the firewall rule will kill the internet for the connecting containers when VPN gets disconnected but the VPN container is still running? I mean can I open console and disconnect VPN and test from my firefox container? 

2 hours ago, bhavdeep said:

Is there a way to test if the firewall rule will kill the internet for the connecting containers when VPN gets disconnected but the VPN container is still running?

Not really but it is indeed working for me and no traffic is going through when the FIREWALL variable is defined.

 

2 hours ago, bhavdeep said:

I mean can I open console and disconnect VPN and test from my firefox container?

You would need to do that from the OpenVPN container, but the container should reconnect if you stop the connection from the terminal, depending on how you try to do that, I've actually never tried that...

 

However as said above, if the connection drops and the variable with the Key: FIREWALL is defined (no need for a Value) it will work fine.

17 hours ago, ich777 said:

Not really but it is indeed working for me and no traffic is going through when the FIREWALL variable is defined.

 

You would need to do that from the OpenVPN container, but the container should reconnect if you stop the connection from the terminal, depending on how you try to do that, I've actually never tried that...

 

However as said above, if the connection drops and the variable with the Key: FIREWALL is defined (no need for a Value) it will work fine.

 

All right. Thanks.

I also set up another container to restart automatically using your instructions from earlier this year below. I had to google a couple of things but glad I did because I learnt more. I'm new to Unraid and the Linux ecosystem.

 

On 4/12/2024 at 12:11 AM, ich777 said:

Please create a variable in the template:

Key: CONNECTED_CONTAINERS

Value: 27286

(This will enable the Connected Containers service)

 

For my containers it's pretty simply, also create a variable in the templates:

Key: CONNECTED_CONTAINERS

Value: 127.0.0.1:27286

 

For these containers you have to place one script on your server, let's say to /mnt/user/appdata/scripts/connected-containers-alpine.sh (make sure the script is executable on the host) and then mount it to the container like:

Container Path: /etc/cont-init.d/91-connected-containers

Host Path: /mnt/user/appdata/scripts/connected-containers-alpine.sh

Access Mode: Read Only

 

 

With that all containers should restart with OpenVPN-Client when you restart the OpenVPN-Client container.

 

Please make sure that all containers have:

in them so that the container actually restarts.

 

Of course all of that will only work if you connected them with:

--net=container:OpenVPN-Client

 

 

FYI, my VPN container ran fine for a few hours and then I lost connection in my other container. And seemed like the VPN container wasn't able to connect to my VPN, so I decided to change the ovpn file, I renamed the original one to VPN_LS.ovpn and copied a new vpn.ovpn to connect to a different server. This seemed to break the container with the following errors in the log:

Error: ipv4: FIB table does not exist.
Dump terminated
grep: /vpn/vpn.conf: No such file or directory
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Starting service for connected containers on port: 27286---
ERROR: VPN not configured!
ERROR: VPN CA cert missing!

 

I tried renaming the new file and reverting the original file to vpn.ovpn and had the same issue. I was about to post my error here when I tried deleting the renamed file so only one ovpn file existed in the appdata/openvpn-client directory and that seemed to have resolved my issue. So seems like there can only be one ovpn file in that directory, even if the other file is named something like vpnxx.ovpn.

 

7 minutes ago, New to Unraid User said:

I tried renaming the new file and reverting the original file to vpn.ovpn and had the same issue. I was about to post my error here when I tried deleting the renamed file so only one ovpn file existed in the appdata/openvpn-client directory and that seemed to have resolved my issue. So seems like there can only be one ovpn file in that directory, even if the other file is named something like vpnxx.ovpn.

You can create a folder in that directory named "backup" or something like that and move the old vpn.ovpn file in there, you can only place one vpn.ovpn in the main directory otherwise the container won't work properly.

 

7 minutes ago, New to Unraid User said:

FYI, my VPN container ran fine for a few hours and then I lost connection in my other container. And seemed like the VPN container wasn't able to connect to my VPN

Did you also specify a server to ping or did you leave that empty?

Hi Ich777,  Ive been using your Sonarr container for a long time now but since the recent unraid update it seems my sonarr cannot communicate with Prowlarr, I get this error -

Unable to connect to indexer, indexer's server is unavailable. Try again later. HTTP request failed: [500:InternalServerError] [GET] at [http://192.168.100.15:9696/3/api?t=caps&apikey=dbcf8b*****************

 

 

Same with the Radarr container too, which reports 

Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. An error occurred while sending the request.

 

 

Are you able to help with this? or is it an unraid update thing.

 

Thanks

Edited November 30, 20241 yr by dgs2001
add info

22 minutes ago, dgs2001 said:

Are you able to help with this? or is it an unraid update thing.

I assume you rely on Allow Host Access in the Docker settings correct?

If so try to restart your Docker service once.

 

It's a bit hard since I don't know what IP that from above is, your Unraid or a container IP running on br0...

4 hours ago, ich777 said:

I assume you rely on Allow Host Access in the Docker settings correct?

If so try to restart your Docker service once.

 

It's a bit hard since I don't know what IP that from above is, your Unraid or a container IP running on br0...

thanks tried a restart of the docker service, but no change. that IP is my LAN, the server and my whole network is IPV4 with IPV6 dissabled.

 

The dockers (sonarr, Radarr and prowlarr) are on the same machine, but prowlarr is routed through a vpn contaioner which I'm starting to suspect is the problem.

 

its Nordlynx and is showing a status of unhealthy, although its still connecting according to the logs.

Im going to downgrade to 6.12.13 which should help me isolate when the problem started and if it was during the change to 6.12.14

Edited November 30, 20241 yr by dgs2001

5 minutes ago, dgs2001 said:

thanks tried a restart of the docker service, but no change. that IP is my LAN, the server and my whole network is IPV4 with IPV6 dissabled.

But is that an IP on sour local network or from your server or a dedicated IP for the container?

Are all containers in the same network or do you use different networks for your containers?

 

It is hard to diagnose what‘s the issue but it seems like that radarr/sonarr can‘t communicate with the container that you use to provide search results.

On 11/28/2024 at 1:29 AM, ich777 said:

Did you also specify a server to ping or did you leave that empty?

 

Yes, I have it pinging google.com every 40 seconds. The VPN reconnects multiple times a day, not sure why. I have FastVPN by NameCheap.com.

 

Also, it looks like the related containers are not restarting. They only restart when I edit some setting on the vpn container. But other than that, they don't restart when VPN container restarts due to ping fail.

 

I'm attaching the logs from the VPN container when the ping fails and it restarts and does not restart the connected containers. The 216.x.x.x address is the VPN endpoint. I am on Unraid 7 beta4.

 

I'm also attaching logs of when I edit something in the Edit page and save. This triggers the connected containers to restart after maybe 10 seconds or so.

 

Thank you for the help.

logs vpn container when it restarts due to failed ping.txt

logs vpn container when I make a change on the edit page and save.txt

Edited November 30, 20241 yr by New to Unraid User

45 minutes ago, New to Unraid User said:

The VPN reconnects multiple times a day, not sure why.

Maybe your Internet connection is flakey or the VPN itself.

 

46 minutes ago, New to Unraid User said:

They only restart when I edit some setting on the vpn container.

This is expected behaviour.

 

46 minutes ago, New to Unraid User said:

Also, it looks like the related containers are not restarting.

Do you use the Connected Containers feature, if yes with which containers?

55 minutes ago, ich777 said:

Maybe your Internet connection is flakey or the VPN itself.

 

Do you use the Connected Containers feature, if yes with which containers?

Should not be an issue with the Internet connection, it's been solid. Maybe the VPN? I've had it for a couple of years but very rarely use it.

I'm still just testing, but for the connected container, I have added "--restart=unless-stopped --net=container:OpenVPN-Client" to the extra parameters. Is there something else I need to do? The 2 containers I'm testing with is Linuxserver Qbittorrent and linuxserver Firefox.

11 hours ago, New to Unraid User said:

Should not be an issue with the Internet connection, it's been solid. Maybe the VPN? I've had it for a couple of years but very rarely use it.

Maybe the VPN but I really can't tell...

 

11 hours ago, New to Unraid User said:

Is there something else I need to do?

A lot, the connected containers doesn't restart on their own, I've built a Connected Containers feature for my containers and made a script for Binhex and Linuxserver containers which should restart the containers that you have to mount to the connected containers, my containers that have the feature built in should restart right OOB.

 

I did a full writeup here:

The scripts are located here:

https://github.com/ich777/docker-openvpn-client/tree/master/connected-containers_scripts

20 hours ago, ich777 said:

A lot, the connected containers doesn't restart on their own, I've built a Connected Containers feature for my containers and made a script for Binhex and Linuxserver containers which should restart the containers that you have to mount to the connected containers, my containers that have the feature built in should restart right OOB.

 

I did a full writeup here:

The scripts are located here:

https://github.com/ich777/docker-openvpn-client/tree/master/connected-containers_scripts

Thank you. I followed your write up earlier including downloading the script file and placing it in appdata/scripts but I didn't understand clearly and created the script path in the VPN container.

I have now put it in the connected container, and after fixing an error, it's working fine. I had 1 VPN disconnect in the last 6 hours and the 2 connected containers gracefully restarted upon VPN container restart.

 

The issue I ran into was in the linuxserver Firefox container with this log- 

---Connection to connected container lost, restarting in 15 seconds...---
/etc/cont-init.d/91-connected-containers: 5: kill: Illegal option -S
---Couldn't connect to connected containers---

I asked ChatGPT and it said "the version of kill available in the container does not support the -SIGTERM syntax for sending signals", it asked me to use "kill -15 1" instead of "kill -SIGTERM 1" and that actually worked.

Explanation was : 15 is the numeric signal value for SIGTERM, On systems with minimal utilities, kill often only supports numeric signal values or simpler syntax. I'm new to linux, but I'm assuming that means the Firefox docker has minimal utilities to keep it small? I did not test with Qbittorrent as both containers are using the same script that now has 15 instead of SIGTERM.

Thank you for the help!!!

I'll go ahead and install your radarr and sonarr containers as well.

 

Oh, and one more thing. Not sure if earlier versions had it, but for Unraid 7, I don't have to select "none" in the network type when setting up the containers, I can choose "container" in the drop down and then select the container name in the next drop down, in this case the VPN container.

 

Thanks again! 

 

Edited December 2, 20241 yr by New to Unraid User
words

Hello!

I'm running unraid 6.12.13 and updated PP today. After restart i see a blank page saying: "Version 17 of JVM is not suitable for this product. Version: 21 or greater is required."
Does someone has a hint for me solving this issue? Thanks in advance!

Since today, Portfolio Perfomance doesn't start anymore. "Something went wrong, can't get latest version of Portfolio-Performance, putting container into sleep mode" is written in log.

5 hours ago, Chlorgas said:

PP

 

5 hours ago, Teleminator said:

Portfolio Perfomance

Please give me a bit, I look into this and report back when it‘s fixed.

@Chlorgas & @Teleminator Portfolio Performance is now fixed.

 

Please update the container itself by enabling the Advanced View on the top right of the Docker page and click on force update at the container, please don't forget to disable the Advanced View again.

Thanks for the fast support, @ich777. Everything seems up and running again!

Thank you, @ich777! It works again.

how does one setup lucky backup to mirror from a server down onto your unraid server? i have tried generating ssh keys and uploading them onto the server. But when I run it. i get connection closed instantly. On the remote option. There is what looks like a spot to put a password, but there is no option for filling a password. I am not sure which side should be doing ssh key generation.

1 hour ago, Goldmaster said:

how does one setup lucky backup to mirror from a server down onto your unraid server? i have tried generating ssh keys and uploading them onto the server. But when I run it. i get connection closed instantly. On the remote option. There is what looks like a spot to put a password, but there is no option for filling a password. I am not sure which side should be doing ssh key generation.

You actually don‘t have to generate keys since the container does that on first start.

 

Please look at the third recommended post on top of this thread.

5 hours ago, ich777 said:

Please look at the third recommended post on top of this thread.

Thank you sods law again is that I was able to copy the .pub file to the server. Then under remote logged with the username and host. Then set as source. The for source field, paste in the directory folder that's on the server. Then for destination, set as the unraid server and that's it.