Jump to content

Squid

Administrators
  • Joined

  • Last visited

  1. Awesome. Once this version is out of beta you’ll have to switch back to the other version. But if you do notice any oddities let me know. It’s safe to run but beyond the basics I haven’t gone through with a fine tooth comb on versions earlier than 7.2 and anything you happen to notice just during normal use saves me a ton of work. FCP will probably yell at you for an unknown plugin installed so just ignore that. You also now wind up in the credits as a tester lol
  2. @TwistedCarnivore @snidera Can you try this and tell me if this fixes your issues. Uninstall Community Applications from the plugins tab. Then in the Install Plugin section paste this in there: https://raw.githubusercontent.com/unraid/community.applications/refs/heads/css/plugins/community.applications-css.plg You may see a popup saying it's taking longer than expected etc but curious if this does fix it. Timeouts are adjusted, and also need to know if any display issues etc show on 7.0/7.1 (shouldn't be though). You don't need to test anything specifically though. It's a major revamp of the CSS
  3. If the source had been in the same GH user then it winds up being a new plugin. A new plugin gets flagged and I receive a notification, and until the plugins are code-reviewed etc etc the they aren't available. In other words, I would've seen the same thing and not approved it. Similarly, if Limetech or anyone else decided to publish a brand new plugin for the OS that fixes everything including the kitchen sink then it better not happen while I'm asleep - nobody gets a free pass on plugins - no exceptions. 99.999% sure the chain of events was done harmlessly, but either way security trumps everything else. I'd rather have this happen (and rediscover that the situation is better than coffee to wake up with) than something slipping through.
  4. Yeah. Every plugin published by Limetech wound up being blacklisted depending upon where you looked (blacklisted in Action Centre, but not blacklisted elsewhere) Reason is that another maintainer wound up forking the templates for them and put them into his own published repository. Backend realizes that the plugins he's effectively trying to publish (hopefully inadvertently) have the source code in a repository hosted by another user (in this case Limetech). Since the user publishing the templates and the user with the source code aren't the same, the feed to maintain the security and integrity of the system blacklists the plugins because there is something going on that is implicitly shady. That maintainer has now been removed from the lists to recover from this. Or put another way, the system did work as designed to protect the user base. The feed has now recovered, and while the blacklistings were correct and proper nobody was in any danger and the circumstance that led to the blacklist has been resolved
  5. I'd love to see the debugging from the older version of CA running on your system. But, as for come down rather quickly: 2025-06-15 21:30:31 DOWNLOAD https://assets.ca.unraid.net/feed/applicationFeed-lastUpdated.json Time: 3 RESULT: string(44) "{ "last_updated_timestamp": 1750036127 }" It took 3 seconds to download 44 bytes. The primary feed aborted after 20 seconds. The backup server with a longer timeout aborted after 45 seconds. I'd try setting static DNS addresses in Settings - Network Settings of 208.67.222.222 and 208.67.220.220, and don't run Unraid through pfSense as a test
  6. Reboot, upgrade Connect, just for safety reboot again. Then install / update CA. There was an issue with an update to Connect a while back that caused this
  7. Is this an inconvenience or an actual issue? I haven't looked at the coding just yet, but its likely part of the security system. Just want to know how much of an issue this is before I look at allowing exceptions in security.
  8. ZippoX started following Squid
  9. bamf270 started following Squid
  10. Dustino started following Squid
  11. xd84 started following Squid
  12. Internet access is working for you. The first very small file CA tried to download (to see if it needs to download the larger file) succeeded. The main download failed after 20 seconds. CA switched to the backup for the file, and it failed after 45 seconds. 99.9% of the time, this file will download within 1-2 seconds on anybody's internet. I'd reset your modem/router
  13. Use the KEY_FILE environment variable instead and toss the file into the appdata share
  14. Changing the file name actually makes my life a ton easier in this circumstances. As of this moment, the messaging from FCP is correct. Ignoring the Open Files / File Activity / Enhanced Log, folder view is a different situation with no drama and you should be installing folder.view2.plg from Apps
  15. Replacement now published No it doesn't Replacement Theme Engine is now within Apps. Uninstall the original from the plugins tab and reinstall the new one from Apps Note that this plugin will be 100% marked as incompatible with 7.2.x as things are vastly different in the coming release.
  16. I don't ignore people until I know them better ;)
  17. Best suggestion right now would be to edit /config/plugins/pinned_appsV2.json on the flash drive. Your idea is a good one, but likely won't make it into the code base for awhile
  18. Because the issue that resulted in it being pulled from CA was rectified yesterday, but nobody informed me... If there's no other problem it should appear within 2 hours
  19. @EDACerton has marked the plugin as being incompatible with OS versions < 7.0 (Not sure why TBH). Directions on installing previous versions can be found in the plugin support thread for it.