cheesemarathon

Members
  • Posts

    339
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by cheesemarathon

  1. The only way is to open advanced mode on the docker page, then force update the container. I don't know of any automated way. @Squid will auto update no longer work for this image?
  2. This page will provide support for setting up BOINC specifically on unRAID. It's seems with your question is more about grcpool not related to unRAID, so here is not the best place to ask.
  3. The creator of the image this template uses has put up an EOL notice on the image. As such he is no longer pushing builds for it. I'm working on an alternative, in the mean time, you could potentially build the image yourself from the github repo. https://github.com/ConSol/docker-headless-vnc-container
  4. I am using ghost my self and it is up 24/7 no issues for me. I don't have it on auto update, so that could be causing issues. Until we have some logs it's going to be hard to find the problem. You might be able to find some bugs in the logs in your database.
  5. I understand the idea behind the change but personally I think it's a PITA. I do not create the docker image, just the unraid template. As such I have no control over the docker image host. Now I will have to make any users of the template aware that to update it they must open advanced options and force an update. Does this change affect the way automatic updates work? Will the script not attempt a pull as unraid says its unavailable?
  6. I use the Oauth2 Proxy template which uses the image quay.io/pusher/oauth2_proxy unRAID used to show that an update was always available, even if that wasn't the case. This wasn't an issue as I would just do a manual update every now and again. However, I have recently noticed it is now showing Update Unavailable preventing my from pulling any updates. I can open advanced mode and force an update, but its not ideal. I have just updated to 6.8.3, so not sure if this issue was introduced then. Is there anything that can do done to fix/change this behaviour.
  7. Try adding the variable database__connection__port with the port of your running the database on.
  8. In my case I'm running MySQL on my unRAID machine. My unRAID machine has an IP of 192.168.1.41 so that is the IP I used in the Ghost docker template. No port number was necessary for me. Can you confirm that you can connect to the database with the same details from another service? Maybe try some database administration software like HeidiSQL
  9. Hey @Josh.5 Thanks for making LANcache Bundle! Just in the process of depreciating Steamcache bundle in favour of your LANcache Bundle! So things may get a little busier here 😛 Thanks again!
  10. @dockerPolice @Squid Hi Both @mlebjerg and I are depreciating steamcache bundle in favour of using Lancache bundle by Josh.5 Is it possible to notify all current users of steamcache bundle. What's the easiest way to have it removed from CA?
  11. Your a star! I love your videos! Please keep doing what your doing 😊 I'm sure this will help lots of people.
  12. I would assume either would work but seeing as I don't know anything about your reverse proxy setup I can't comment. If you can't get it to work, please post some more info.
  13. https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-admin-page In short, use any tool you like to generate something random. You could also slap your keyboard a few times.... 🤣 But it can be anything you like, it's just a password.
  14. You might have to do a custom config then. I have no experience with proxy manager but post a pic of your setup I'll see if I can spot anything.
  15. Are you able to access bitwarden on the domain you have set up. Try browsing to the url in the error above. Check the nginx config here: https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples
  16. Open Cloud Commander, click the settings cog button and at the top. Enable auth and set a username & password. If your using a reverse proxy to access remotely, you can add auth to that instead if you want. several options like a htaccess file or Oauth2proxy
  17. I have bitwarden working with the newest template without SMTP. I suggest you follow the support link to the github repo. The wiki there has a lot of info which should help. Otherwise open an issue on github for some help as i no longer maintain this template.
  18. Regarding the admin thing. That's a question for the new bitwarden_rs maintainers. I no longer maintain the template, hence the depreciation notice. Follow the support link in the new template
  19. This is exactly what you should do! Thanks for the excellent instructions!
  20. Your in the correct place. There must be something in that page that chrome doesn't like. If I remember correctly, Firefox is also included so you could try that. This docker container is EOL now anyway so I'm working on a replacement.
  21. The only other thing I can think is that your browser is caching the settings somehow. Failing that, open an issue at https://github.com/coderaiser/cloudcmd
  22. I assume your referring to migrating bitwarden. Yes you can remove your existing container, don't delete your appdata. Then add the new one from CA and point it to your existing appdata. This worked for me anyway!
  23. If they window is too small for two panels it will show only one. Like on mobile for example. You can also check the .cloudcmd.json file in your appdata directory. This contains all the settings. Look for "oneFilePanel" this should be set to false.
  24. Are you using my template or the new one currently available in CA? Regardless it just sounds the the Web UI setting is wrong in the unraid template. Just change the port there.