diehardbattery

Members
  • Posts

    61
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

diehardbattery's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. Can someone please help? Not everyone knows how to resolve these issues independently and unfortunately, I am one of them. I just want this working again...
  2. No I haven't done anything other than run the command you provided earlier... When I Click show more there is nothing. The arow moves up as if to show more info but there's nothing there:
  3. Okay, I ran the command but now when I try to access I get this error: Configuration was not read or initialized correctly, not overwriting /var/www/html/config/config.php I tried changing permissions for everything in the /config folder to 777 but that does not work either. I restored a backup that was made from the CA appdata backup utility and ran the upgrade command again. After restarting the container, it appears the docker log is still complaining about user id 33. I have not done anything custom that I am aware of that would make the current user id what it is (99)? Initializing nextcloud 28.0.3.2 ... Upgrading nextcloud from 28.0.2.5 ... => Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/pre-upgrade Console has to be executed with the user that owns the file config/config.php Current user id: 33 Owner id of config.php: 99 Try adding 'sudo -u #99' to the beginning of the command (without the single quotes)
  4. Should -u 33 be -u 99? When I run it, I get this: Console has to be executed with the user that owns the file config/config.php Current user id: 33 Owner id of config.php: 99
  5. So I ran into this when trying to access my instance today... and I can't make heads or tails on how to proceed. Unfortunately I'm not very good at translating stuff from other nexcloud variants (aio, etc). Trying to update via the unraid docker page shows everything is up to date.
  6. Having an issue with the cronjob container: 1. I installed the cronjob container. Now my Admin overview gives the following error: It was not possible to execute the cron job via CLI. The following technical errors have appeared: - Your data directory is readable by other users. Please change the permissions to 0770 so that the directory cannot be listed by other users. Changing the data directory to 0770 says the directory is invalid when I restart the container and can't go anywhere...
  7. Gotcha... if the key is good enough then I'll probably just leave it at that
  8. Okay, a bit off topic, but how would that work if I wanted to connect via cloudflare tunnel? I have an A record for the domain currently, and it appears I'm unable to add a tunnel with that because it says there's already a record with the name and the documentation they reference to troubleshoot, it seems a bit confusing to me. As for the exe file, are you referring to the exe for the client? That's all I have installed on Windows, the rest is on Unraid.
  9. Yeah, that's why I'm doing the port forwarding.. its just that I'm not sure why swag still seems to want to intercept it and I am reasonably sure that I have the port forwarding setup correctly in OPNSense... UPDATE: I found the public key in the logs and pasted it into the key field on the client with nothing else. Now it works, even from outside access. How safe is this? Should I continue to try and get my subdomain working? Would I still need the public key in that case?
  10. Trying to get Rustdesk-AIO running from my cloudlfare domain (have tried proxied and dns only). I know that part seems to be working. But as I understand it, Rustdesk shouldnt use a reverse proxy. I have swag running, and every time I try to access my rustdesk domain I get the swag welcome page. I have a router running OPNSense and believe I have the port forwarding correct. However it's still not working. What am I missing?
  11. Just recently I noticed that my services using swag stopped working. Upon checking the logs I found what you see in the screenshots. Using WinSCP, I checked the keys folder, and the permissions appear to be correct. I have not changed anything so I dont know what caused this.
  12. I came across this guide, which seems to be the easiest way to get Nextcloud up and running. Wondering if anyone else has done this, and if so, how do you setup the shares? The guide seems to leave this out unless I'm misreading something? Note: The only thing I did differently from the guide is to use Portainer-CI as it seems Portainer-CE isn't available anymore?
  13. Not sure where to look... nice number of percent full though lol... diagnostics-20230824-0926.zip
  14. Okay, I think I get it now. This is my first rodeo with this type of situation so just questioning every little thing lol.