2 hours ago, ich777 said:

Funny story, I just implemented a ping check yesterday so the container auto restarts when the connection is lost and I even implemented something that I call Connected Containers so that if the VPN container is restarted for whatever reason, compatible containers with Connected Containers will restart too.

 

 

Awesome, I've added the variables and did the update. My main ones I'm using are basically Qbitorrent and most of the *arr suite. 

 

I don't know how quickly they freak if they lose access to download client or indexer. I'm betting 5 minutes can get past them if needed. 

 

I'll let this run and see what I can see as far as if this gets me past my issue or not. Thanks for the help. If you need the actual container names off github let me know and I can list them. I'm HOPING that I won't need to worry about bouncing the other containers if this guy notices and responds quickly enough. 

 

Whatever happens, thanks for all your effort on this. It's appreciated. 

Just now, Merijeek said:

I don't know how quickly they freak if they lose access to download client or indexer. I'm betting 5 minutes can get past them if needed. 

The main issue with that is, when the container restarts all the containers which are routed through the container need to be restarted too and that's why I came up with that idea "Connected Containers".

 

Just now, Merijeek said:

I'll let this run and see what I can see as far as if this gets me past my issue or not. Thanks for the help. If you need the actual container names off github let me know and I can list them.

I just need the container names and from which repository/maintainer since I have to look into if that can be implemented easily, if you are using my *arr containers then it is pretty simple.

6 minutes ago, ich777 said:

Please check the variable in the container, it seems to be set incorrectly to "lastest" instead of "latest".

 

It should look like that:

oh my god that is embarrassing....

Thank you very much, that did the trick! Damn sausage fingers!

26 minutes ago, ich777 said:

if you are using my *arr containers then it is pretty simple.

Not using yours, though not for any particular reason. I'm sure there's a difference between, say, your Sonarr and linuxserer's, but I never put too much thought into it.

 

Looks like I've got these of yours: 

ich777/sonarr                    
ich777/radarr                    
ich777/openvpn-client            
ich777/lidarr                    

 

And a bunch that aren't:

ghcr.io/mealie-recipes/mealie   
linuxserver/jackett             
binhex/arch-readarr             
lscr.io/linuxserver/duckdns     
binhex/arch-readarr             
netdata/netdata                 
lscr.io/linuxserver/calibre     
lscr.io/linuxserver/bazarr      
binhex/arch-overseerr           
binhex/arch-jellyfin            
binhex/arch-plexpass            
binhex/arch-prowlarr            
hotio/overseerr                 
binhex/arch-readarr             
ghcr.io/advplyr/audiobookshelf  
ghcr.io/ajnart/homarr           
gotson/komga                    
binhex/arch-readarr             
deasmi/unraid-tailscale         
jlesage/jdownloader-2           
jlesage/dupeguru                
jlesage/nginx-proxy-manager     
cr.hotio.dev/hotio/qbittorrent  
jaymoulin/jdownloader           
tzahi12345/youtubedl-material   

 

Honestly, I have zero issues switching them over. I can't imagine they'd be that difficult. If it'd help.

 

17 minutes ago, Merijeek said:

Honestly, I have zero issues switching them over.

You don‘t have to switch them over I think.

Do you route all containers through the VPN container?

 

Only the ones that you route through the VPN container are necessary to restart.

12 minutes ago, ich777 said:

Only the ones that you route through the VPN container are necessary to restart.

Good point. In that case it'd be Jackett, all the Arrs, and Qbittorrent. 

20 minutes ago, Merijeek said:

Good point. In that case it'd be Jackett, all the Arrs, and Qbittorrent. 

I‘ll look into the containers whats needed to be done.

11 hours ago, Merijeek said:

ich777/openvpn-client            

Please create a variable in the template:

Key: CONNECTED_CONTAINERS

Value: 27286

(This will enable the Connected Containers service)

 

11 hours ago, Merijeek said:

ich777/sonarr                    
ich777/radarr                    
ich777/lidarr          

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

Key: CONNECTED_CONTAINERS

Value: 127.0.0.1:27286

 

12 hours ago, Merijeek said:

linuxserver/jackett             

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

 

13 hours ago, AgentXXL said:

Any chance of similar functionality in your containers?

Please update the container itself and add a variable to the template:

Key: NOVNC_TITLE

Value: Your .-_ Title

(Only alphanumeric, numeric, spaces and . - _ are allowed)

 

Looks like that:

Can anyone assist in getting browser sync working in the chromium docker?  It seems to have the default Deb API keys so assumed that would be enough, but when i sign in it goes through ok but doesnt start the sync process.

20 minutes ago, joshdinsdale said:

Can anyone assist in getting browser sync working in the chromium docker?  It seems to have the default Deb API keys so assumed that would be enough, but when i sign in it goes through ok but doesnt start the sync process.

Is this the feature where you log in to your account and it should sync?

If yes, this isn't supported anymore with Chromium, Google only allows that from a real Chrome browser.

4 minutes ago, ich777 said:

Is this the feature where you log in to your account and it should sync?

If yes, this isn't supported anymore with Chromium, Google only allows that from a real Chrome browser.

 

I've actually just solved this.

 

As per this page https://stackoverflow.com/questions/67459316/enabling-chromium-to-sync-with-google-account, you can add the specified oauth2 details to chromium.

 

I did this by adding a new Variable in the docker settings called EXTRA_PARAMETERS and setting the value to --oauth2-client-id=77185425430.apps.googleusercontent.com --oauth2-client-secret=OTJgUOQcT7lO7GsGZq2G4IlT

 

Not sure how long this workaround will last but will do me for now!

 

5 hours ago, ich777 said:

Please update the container itself and add a variable to the template:

Key: NOVNC_TITLE

Value: Your .-_ Title

(Only alphanumeric, numeric, spaces and . - _ are allowed)

 

Looks like that:

Thanks for this! Works perfectly.

I have been getting this sync error. I have already tried to delete and add the backup again. I even logged into my Mega account and deleted everything and started over. As soon as "media" start syncing it gets disabled. I have been running the app for months and this just started happening within the last few days.

48 minutes ago, iatemenchi said:

I have been running the app for months and this just started happening within the last few days.

This is strange, I just upsated the container a few days ago, maybe that‘s the cause of the issue, I will look into it, please give me a few days.

 

So only this one folder is affected correct?

3 minutes ago, ich777 said:

This is strange, I just upsated the container a few days ago, maybe that‘s the cause of the issue, I will look into it, please give me a few days.

 

So only this one folder is affected correct?

Occasionally one of the other drives will be disabled (i never looked to see why) and I would reenable and all is good. However, the media drive is the only one with this issue and today is the first day this issue has come up. I've been updating my media drive heavily over the last few weeks so I have been monitoring the app consistently.

35 minutes ago, iatemenchi said:

However, the media drive is the only one with this issue and today is the first day this issue has come up.

Is this folder mounted or shared via NFS by any chance?

5 minutes ago, ich777 said:

Is this folder mounted or shared via NFS by any chance?

Mounted and shared by SMB.

3 minutes ago, iatemenchi said:

Mounted and shared by SMB.

Can this be the cause of the issue? I‘m not able to reproduce that over here.

 

Have you upgraded Unraid recently or changed something in the share settings?

9 minutes ago, ich777 said:

Can this be the cause of the issue? I‘m not able to reproduce that over here.

 

Have you upgraded Unraid recently or changed something in the share settings?

Unraid was updated a few days ago. No changes were made to share settings. And now 2 of my 3 drives are getting disable with the same error.

Just now, iatemenchi said:

And now 2 of my 3 drives are getting disable with the same error.

What do you mean with getting disabled? In the Mega app or on Unraid?

Just now, ich777 said:

What do you mean with getting disabled? In the Mega app or on Unraid?

Within the app. I can still use the drives no problem outside of the app.

 

Now, this is really weird. It seems like its only effecting one drive at a time.

And now all seems fine. Any idea what was happening?

25 minutes ago, iatemenchi said:

And now all seems fine. Any idea what was happening?

Not really...

Maybe this was just a fluke, I really can't tell why that's happening on your system. If it happens again, please feel free to reach out again.

Hi ich!

 

I've been getting lots of issues in the last few days with errors indicating "File fingerprint missing".

If I resolve them I seem to get three copies of each file in the download queue. Quite strange.

 

I have a feeling it's working fine for files that are in sub-directories though, but that could be coincidental.

Any ideas?

 

Cheers