jowi

Members
  • Posts

    1176
  • Joined

  • Last visited

Everything posted by jowi

  1. Yes, and thanks again, but i wanted to follow your advice and wait for some more confirmations. But it doesn't look anyone else will respond. I decided to do it anyway. I've backupped the db data just to be sure, and did the update, all looks well.
  2. I have now asked 4 times in the last few weeks if ANYONE has issues after applying the fix a few weeks ago, and applying recent updates. Sadly, no response at all? Really?
  3. How can i find out what exact version is installed anyway? If i know, i could do the update, and if it fails, revert back to my previous (current) version.
  4. Anyone yet that can confirm that updating a previously 'fixed' mariadb (manually fixed to v10.5.12) can be succesfully updated to the latest version?
  5. What i did was set the version manually (i forgot what version exactly) update it, and then set it to 'latest', and get the lastest version. After that, it was working again. As i understand it, that was the fix: 1. update to version x manually, 2: update that to the latest. So, how can i see what the version is i have actually installed? *edit* if i check version in mariadb itself it says : 10.5.12-MariaDB Don't know if the docker version is something else?
  6. But i did the fix, and now there is an update... so it won't let me skip this update. I have to manually do ALL other updates, otherwise if i ' update all' this will update as well... i will wait for confirmation from others that did the fix and applied this latest update.
  7. Unraid tells me there is an update for the mariadb docker, but i'm affraid to install it, since last time everything went wrong. How do i know this update will be ok? Someone tried it? Is there a way to know to what version it will be updated? Is there a way to rollback? Is there a way to exclude a docker from updates? At the moment, i can not update all, since i dont want mariadb to update, so i have to update all others manually one by one...
  8. It has been working good for the last few days. But i'm worried about the next time unraid wants to update mariadb... is there any news if this will continue to be a problem? Or should we export the db etc and install a new, different mariadb docker?
  9. ok, looks like the same issue others are having, i did not recognize it that fast. Did the 'downgrade' (?) to linuxserver/mariadb:110.4.21mariabionic-ls31 and then to latest... as described. Looks like it is functioning again. Now making sure i do have backups of everything that uses mariadb... something i overlooked.
  10. My mariadb no longer works after the last (?) update? If i run 'mysql' i get : Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) Also several website depending on mariadb and my nextcloud is not working. This is bad... How do i fix this? Can i go back to the previous version, and if yes, how?
  11. Ever since i upgraded to unraid 6.9.2, my timemachine stopped working. Had it set up using spaceinvaders tutorial. Now, whatever i do, tm just cant find the disk where the timemachine share is anymore. Even removed my old timemachine share... (nice, no backups anymore...) hoping i could create a new one, or maybe the tm share got to big, but no matter what i do, i just can't get this f-ing thing to work on unraid. It was always a hassle, but this time it looks like it's really broken.
  12. Found the answer on Reddit. Not here. On Reddit. Just upgrade to 6.9.2 and it is fixed.
  13. Doesn't work... after manually forcing all updates, basic mode shows 'up to date', so far so good. But if i now check for updates, everything reverts back to 'not available' again... So, what is the exact solution to this?
  14. Not what i was looking for but i found a tutorial in the french section that had the info i needed:
  15. Some months ago i used this topic to run a wordpress container, and i recall walking through a step by step description (like spaceinvaders tutorials) on how to add the mariadb, how to create the db etc but i can't seem to find it anymore? Is there a step by step tutorial anywhere on how to set up a new wordpress site on unraid?
  16. yeah i tried some more renewing and recreating certificates, and all of a sudden it worked. Well, for me it always worked, but i now have new certificates... still don’t understand why the ping doesnt work, but for me everything is fine... 👍
  17. Weird, everything pings fine from here, also, all domains are working fine over 4G on my phone... nextcloud works, i’ve got a wordpress site that runs etc. all is good as far as i cab tell? I dont get it.
  18. But to be clear, if you ping nextcloud.20ten.nl , you get a timeout as well?
  19. The ziggo modem is in bridge mode; so shouldn't have any port forwarding / firewall etc. I'm using pfsense as router, there is port fwding configured (1443/180 to https/http 443/80 internally on unraid for nginx proxymngr) Will reboot the modem anyway.
  20. External ip is correct. Also curl ifconfig.me shows the same. According to hosting provider my domains do resolve OK: https://dnschecker.org/#A/nextcloud.20ten.nl https://dnschecker.org/#A/dehef.20ten.nl Ip is a cable modem from a local ISP. For the rest everything is working fine here on my side of the modem... pinging to it works fine from my side: 77.248.64.xxroot@UNRAID:/etc# ping 77.248.64.xx PING 77.248.64.xx (77.248.64.xx) 56(84) bytes of data. 64 bytes from 77.248.64.xx: icmp_seq=1 ttl=64 time=0.140 ms 64 bytes from 77.248.64.xx: icmp_seq=2 ttl=64 time=0.150 ms 64 bytes from 77.248.64.xx: icmp_seq=3 ttl=64 time=0.122 ms 64 bytes from 77.248.64.xx: icmp_seq=4 ttl=64 time=0.137 ms 64 bytes from 77.248.64.xx: icmp_seq=5 ttl=64 time=0.124 ms 64 bytes from 77.248.64.xx: icmp_seq=6 ttl=64 time=0.166 ms 64 bytes from 77.248.64.xx: icmp_seq=7 ttl=64 time=0.131 ms ^C --- 77.248.64.xx ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6146ms rtt min/avg/max/mdev = 0.122/0.138/0.166/0.014 ms bit lost here on what is going on?
  21. External ip is correct (77.248.64.xx) but i can't also ping to it... DNS A records are also correct and pointing to this ip. Nothing has changed as far as i can see. I will contact my hosting provider to see if there is something wrong there. Wouldnt be the first time. What is ACL?
  22. Ah ok, that works... now i get some more info, firewall issues? DNS records? Don't understand, all worked fine, why is it complaining about this for the certificates now all of a sudden? [code] /tmp # certbot renew --dry-run Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/npm-2.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert is due for renewal, auto-renewing... Plugins selected: Authenticator webroot, Installer None Renewing an existing certificate Performing the following challenges: http-01 challenge for nextcloud.20ten.nl Using the webroot path /config/letsencrypt-acme-challenge for all unmatched domains. Waiting for verification... Challenge failed for domain nextcloud.20ten.nl http-01 challenge for nextcloud.20ten.nl Cleaning up challenges Attempting to renew cert (npm-2) from /etc/letsencrypt/renewal/npm-2.conf produced an unexpected error: Some challenges have failed.. Skipping. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/npm-3.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert is due for renewal, auto-renewing... Plugins selected: Authenticator webroot, Installer None Renewing an existing certificate Performing the following challenges: http-01 challenge for documentserver.20ten.nl Using the webroot path /config/letsencrypt-acme-challenge for all unmatched domains. Waiting for verification... Challenge failed for domain documentserver.20ten.nl http-01 challenge for documentserver.20ten.nl Cleaning up challenges Attempting to renew cert (npm-3) from /etc/letsencrypt/renewal/npm-3.conf produced an unexpected error: Some challenges have failed.. Skipping. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/npm-4.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert is due for renewal, auto-renewing... Plugins selected: Authenticator webroot, Installer None Renewing an existing certificate Performing the following challenges: http-01 challenge for dehef.20ten.nl Using the webroot path /config/letsencrypt-acme-challenge for all unmatched domains. Waiting for verification... Challenge failed for domain dehef.20ten.nl http-01 challenge for dehef.20ten.nl Cleaning up challenges Attempting to renew cert (npm-4) from /etc/letsencrypt/renewal/npm-4.conf produced an unexpected error: Some challenges have failed.. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/npm-2/fullchain.pem (failure) /etc/letsencrypt/live/npm-3/fullchain.pem (failure) /etc/letsencrypt/live/npm-4/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ** DRY RUN: simulating 'certbot renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/npm-2/fullchain.pem (failure) /etc/letsencrypt/live/npm-3/fullchain.pem (failure) /etc/letsencrypt/live/npm-4/fullchain.pem (failure) ** DRY RUN: simulating 'certbot renew' close to cert expiry ** (The test certificates above have not been saved.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3 renew failure(s), 0 parse failure(s) IMPORTANT NOTES: - The following errors were reported by the server: Domain: dehef.20ten.nl Type: connection Detail: Fetching http://dehef.20ten.nl/.well-known/acme-challenge/4fd7A4LKzcJxFvt4MYbLvSf6OxWUP5Mtd3xn4Su-HHA: Timeout during connect (likely firewall problem) To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - The following errors were reported by the server: Domain: documentserver.20ten.nl Type: connection Detail: Fetching http://documentserver.20ten.nl/.well-known/acme-challenge/hNPkFB8MC8whRSBugq-sa9O73F0phkv1yRIHAzNAxDc: Timeout during connect (likely firewall problem) To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - The following errors were reported by the server: Domain: nextcloud.20ten.nl Type: connection Detail: Fetching http://nextcloud.20ten.nl/.well-known/acme-challenge/uVRln4-qO9gV1eNfm2ys02uvieIT0GPN0SWe1fB-1F8: Timeout during connect (likely firewall problem) To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. /tmp # [/code]
  23. just 'internal error' and ' timeout'. Probably logged somewhere but i dont know where. Not a guru certbot: command not found???? where is certbot?
  24. I have to renew my certificates, but i'm getting internal errors and timeouts? Also deleted the certificate and trying to get a new one, also same errors. What is the trick with nginx for renewal? I'm using letsencrypt certificates btw. Do i need to run the letsencrypt container as well for this to work? Or can i use some other certificate? From where?
  25. Isn’t that a spinup issue? What happens when you have your array spun up to begin with?