[WireGuard quickstart]

Hi All,

I apologize in advance if this might have been mentioned before, but after doing several google searches with varying search terms and finding some existing reports, none of the troubleshooting steps I came across resolved the issue I am experiencing.

 

Unraid Version: 6.12.6

 

Some background,

My WireGuard Client (Peer) was not working (connection would be established but I would have no network or internet access - configuration in WireGuard on Unraid is set to Remote Tunneled Access) and so in trying to troubleshoot, I tried deleting the Peer from the VPN Manager Settings in Unraid (among other things). Upon re-creating the Peer in Unraid, I am no longer able to download the Peer Configuration. The eye icon is greyed out.

 

In reading some of the other reports on this issue, there are some instances where WireGuard wasn't deleting the old Peer Configurations from the Flash Drive Config Folder and this was causing some issues. For my situation, the Peer Folder on the Flash Drive is empty even though the VPN Manager in Unraid shows I have a Peer setup.

I also tried deleting the Tunnel and peer while monitoring the Config Folder and see the Tunnel configuration gets deleted (there is no Peer data to delete so that folder stays empty), and when I create a new Tunnel, I see those configuration files generated in the Config Folder as well.

 

I'm left scratching my head trying to figure out what's going.

 

Any help is greatly appreciated!

 

Unraid Version: 6.12.6

 

UPDATE: Resolved

It appears the issue manifests if the Peer Name field is left empty. This seems like it is a bug since the default configuration settings indicate the Name Field is Optional.

 

Gonna leave this post in case anyone else encounters the issue too so they can try what worked for me to see if it helps them.

[[Plugin] Appdata.Backup]

On 8/8/2023 at 10:53 PM, alkon_rojo said:

Hi to everyone, and first Thanks so much for this awesome plugin.

 

I'm facing one problem regarding the task of updating a docker during the run, when the same image docker is being use over two dockers:

 

[09.08.2023 04:59:52][Main][info] Auto-Update for 'bazarr' is enabled - checking for update...
[09.08.2023 04:59:53][Main][info] Update available! Installing...
[09.08.2023 05:00:10][Main][info] Update finished (hopefully).
[09.08.2023 05:00:10][Main][info] Auto-Update for 'ApacheGuacamole' is enabled - checking for update...
[09.08.2023 05:00:12][Main][info] No update available.
[09.08.2023 05:00:12][Main][info] Auto-Update for 'bazarr-vo' is enabled - checking for update...
[09.08.2023 05:00:15][Main][info] No update available.
[09.08.2023 05:00:15][Main][info] Auto-Update for 'sonarr-vo' is enabled - checking for update...
[09.08.2023 05:00:18][Main][info] No update available.
[09.08.2023 05:00:18][Main][warning] An error occurred during backup! RETENTION WILL NOT BE CHECKED! Please review the log. If you need further assistance, ask in the support forum.
[09.08.2023 05:00:18][Main][info] DONE! Thanks for using this plugin and have a safe day ;)
[09.08.2023 05:00:18][Main][info] ❤️

 

The problem is for example in this logs the dockers are pulling over the same docker image is "Bazarr" so I have two docker "bazarr" and "bazarr-vo" and when it has a new image version only gets update the first that it finds it, the next docker sharing the same docker image finds that there's no new image to pull, but when it start it doesn't start updated. So this problema is the same with all the dockers that are sharing the same docker image, so only gets update the first that finds the new docker image to be update, the rest never gets update.

 

I was facing several this problem several days ago, but in the community I didn't find anyone with the problem.

 

Thanks to all and best regards.

 

5 hours ago, MadMatt337 said:

Not sure if it is just myself as I don't see reference to it in previous posts but I have noticed my dockers are no longer automatically updating after backup. As far as I can tell this started happening after the 2023.08.16 update. The logs are showing that the dockers are all up to date but in this particular log I have 5 different dockers that have updates available.

backup.log 14.76 kB · 2 downloads

 

2 minutes ago, EthanBezz said:

I can confirm it's not just you, my containers have also not been updating. My logs, like yours, also say that there's no update available for containers which do have updates.

 

I as well can also confirm this issue has been present for a little while now.

[[Support] Linuxserver.io - Transmission]

16 hours ago, cherrybullet said:

You have to stop the container before editing settings. Otherwise, transmission will overwrite any settings when it shuts down and potentially while it's running.

 

I've also experienced rpc issues with the latest update. Been trying to downgrade, but now I can't get authenticated when it was previously enabled and working fine.

Even if I hadn't, a container update shouldn't modify settings values unless it is noted in the change log (which it was not).

I definitely stopped the container before making changes to the settings file though.

 

And, I too changed the repository value to use a previously known working version.

 

For others reporting, it'll be valuable to include the version.

The issue is appears to be specific to version 3.00-r0-ls73 - the changes included in that version, at a glance, do not appear to be valid (are at conflict with themselves) and the commit comments for testing of the changes are not specific. Which would lead me to believe that the person who made the changes only tested that the changes resolved their issue, and did no negative testing to ensure existing functionality was retained.

 

Either way, the issue is still present and there has been no new build pushed for this container as of yet.

Hopefully this matter gets resolved soon.

[[Support] Linuxserver.io - Transmission]

15 minutes ago, yogy said:

I have everything working before the update. Now I cannot enable my password and have no clue how to whitelist hosts.

I shutdown the Transmission container, tried to edit settings.json (/mnt/user/appdata/transmission) with no luck on enabling password again. It keeps going back to false. I can change rpc-host-whitelist entries but nothing I enter there works.

I too am experiencing the same issue after updating (authentication/password settings will not stay enabled/true).