Jump to content

Squid

Community Developer
  • Posts

    28,770
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. https://forums.unraid.net/topic/50490-solved-commands-to-start-and-stop-array/?tab=comments#comment-496967 But you'd first have to add in the csrf token to the end of the line ?csrf_token=xxxxxxxxxxxxxxx via whats listed in /var/local/emhttp/var.ini
  2. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-545988
  3. Do any of the VMs have any special characters in their names? EG: apostrophies / quotes etc
  4. That's not what you asked about. This is what you want then https://forums.unraid.net/topic/57181-real-docker-faq/#comment-566084
  5. make a folder on the flash drive /config/plugins/community.applications/private/xorinzor and toss the xml into there.
  6. All Plugins would be affected, because you can't install any of them. A VM utilizes it's own lookups etc. Did you check the Gateway?
  7. Check that your gateway is set to your router's IP address, and give it static dns addresses of 208.67.220.220 and 208.67.222.222 in Settings / Network
  8. Simply set the CA backup share to use cache : no Sent via telekinesis
  9. Because over time, the docker system and CA (the only other 2 pieces of software that look at that folder) have been updated over time to ignore any corrupted files. This plugin hasn't. I'd open each of them and see if there's any obvious problems and then delete it. If I think about it, I may update the plugin on the weekend, even though it is deprecated
  10. Coruppted XML file in /config/plugins/dockerMan/templates-user.
  11. Post the diagnostics, the applicable VM XML file, and a screenshot of the error.
  12. Just so you know, you will have to redo those steps whenever you update the container.
  13. Seems to me to be more of an issue with OpenVPN. Have you tried posting in the appropriate support thread?
  14. try deleting /config/ssh and /config/ssl on the flash drive and reboot
  15. On the flash drive, delete the contents of config/ssh and config/ssl. Reboot and try again.
  16. Go to Tools - Update OS. Then downgrade to your previous version of unRaid. Reboot then Tools - UpdateOS and upgrade to RC8. Everything will work correctly. RC6 has a bug with plugin installs
  17. Use the GUI. Manually editing xml is fraught with problems.
  18. Plex (or any container running locally on the server) doesn't use SMB to manage the files.
  19. This is what I did: dumped my own bios as per here : https://www.youtube.com/watch?v=mM7ntkiUoPk After that, Windows still showed Code 43, but I downloaded and installed the Nvidia drivers directly and then everything worked out for me.
  20. 10:1 its this:https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566086
  21. In CA settings, you can have it display incompatible apps
  22. Via the Post Arguments field on the template
  23. Couple of questions I'm assuming that this is supposed to be a reverse proxy URL to this container? First stumbling block. I've created an Alexa Developer Account, and can get the Authorization Code, but it's not taking it. Do I need an AWS developer account instead? The directions on GitHub aren't clear, and contradict itself at times (just weary of handing over a CC# if I don't need to) root@55358642ec01:/config# lexigram login --no-browser true ? Please type in your new profile name: Squid -------------------- Initialize CLI -------------------- ? There is no AWS credential setup yet, do you want to continue the initialization? (Default: False) Yes Warning: Profile: "Squid" will not be able to deploy lambda functions since no AWS credentials are set up. Paste the following url to your browser: https://www.amazon.com/ap/oa?redirect_uri=https%3A%2F%2Fs3._blahblahblahAsIveNoIdeaWhatIsPersonallyIdentifiableOrNot ? Please enter your Authorization Code: xxxxxxxxxxxxx Access token failed. Error: getaddrinfo EAI_AGAIN api.amazon.com:443
  24. Wait a couple of minutes, then reload the page. The result(s) should be there. Then you should be able to enable "Avoid Disk SpinUps" which should alleviate this to a certain point. Barring that, it's on the todo list to work around unRaid's hard limit of 120 seconds for any particular operation.
×
×
  • Create New...