infiniterookie

Hi @grtgbln, When you have a moment, it appears that the configuration of your Community Apps Template for Profilarr utilizes the same configuration as the one from one of the Profilarr app developer's Seraphys. After installing either instance, both show as installed even though only one has actually been installed (screenshot attached). For context, I had no previous version of Profilarr installed when discovering this issue. Let me know if you have any questions or need more information 😊

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.

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

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.

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