jowi

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?

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.

Found the answer on Reddit. Not here. On Reddit. Just upgrade to 6.9.2 and it is fixed.

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?

Not what i was looking for but i found a tutorial in the french section that had the info i needed:

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?

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... 👍

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.

But to be clear, if you ping nextcloud.20ten.nl , you get a timeout as well?

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.

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?

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?

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]

just 'internal error' and ' timeout'. Probably logged somewhere but i dont know where. Not a guru certbot: command not found???? where is certbot?

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?

Isn’t that a spinup issue? What happens when you have your array spun up to begin with?

You have to add other folders by editing the docker settings in unraid. There you can add a path on your host system using an alias name, that will show up inside the roon container.

Thanks deleted everything and reinstalled the server, using proper paths this time, now rebuilding again. So far so good.

Got some issues with this: Move the following files and subdirectories from /mnt/cache/appdata/roonserver/RoonServer to /mnt/cache/appdata/roonserver/app/RoonServer/: /Appliance, /RoonMono, /Server, Version, check.sh, and start.sh. In my case, there is no folder "/mnt/cache/appdata/roonserver/RoonServer", just "/mnt/cache/appdata/RoonServer" ... second: Move the following files and subdirectories from /mnt/cache/appdata/roonserver/ to /mnt/cache/appdata/roonserver/data/: /RAATServer, /RoonGoer, and .rmembid. The RAATServer and RoonGoer and .rmembid are NOT located in "/mnt/cache/appdata/roonserver" but in "/mnt/cache/appdata/" itself.... As far as i know i never changed or was asked to change the paths of raatserver and roongoer etc...? So how come these are not in the "/mnt/cache/appdata/roonserver" folder in my case? So in my appdata folder there is RAATServer, RoonGoer and RoonServer. My container path for 'app' is /mnt/cache/appdata/... i guess that is the problem? It should have been "/mnt/cache/appdata/roonserver" ? Should i just remove, reinstall and start over using /mnt/cache/appdata/roonserver for 'app' container path?

Oh but the docker often looses it’s connection to the core anyway, so i end up rebuilding the library every few weeks... so nothing new there

What am i missing if i just update the roon container using docker update in unraid, and update the client from within the app, and have it rebuild my lib or use a previously saved library backup? Why do i need all he steps described above?

Parity check is ok. Average of about 130Mb/s. CPU looks ok to. The delay seems to be a reiserfs issue where it is replaying transactions after a dirty powerdown. The server sometimes just stops responding totally and needs rebooting, Why this is is a mystery still.

Well it’s 9 disks, so maybe its 30-40 seconds a disk, i don’t know, i can’t see what is actually happening.... and yes this is from power off. Again, all this time the gui is unavailable, i can only see what is happening in a console and looking at /mnt to see that after a few minutes (!) after restart/reboot, disk1 appears and then after 30-40-50 seconds disk2 etc. Once all the disks incl. /user and /cache show up, the gui starts. i’ll try to add diagnostics but that also takes forever to complete...

I notice that after a reboot, once i get the unraid login (with ipmi) the array/disks are not up yet. In fact, it takes 4-6 minutes for the disks to show up? They get online one by one... disk1.... few minutes later disk 2... etc. The last to arrive is user and cache. Why is this? I never had this with previous versions? Everytime i reboot i'm scared to death, where are my discs? What is happening? Also, until the array is online, there is NO GUI... so you can't see what is going on. There is only a prompt if you login. So after a reboot, which basically takes 30-40 seconds, you are left in the dark for 4-6 minutes in which you can not do anything... surely this is not by design?

Ok... this is getting silly. Now i've re-installed everything (including database) and now i can view the site from my domain, also the wp-admin, but NOT from my unraid machine... if i go to wp using unraid webui (so to my 192.168.xx.yy:port) it complains about ERR_SSL_PROTOCOL_ERROR, while SSL is NOT configured. I'm really starting to hate wordpress now.