JoHimself

In case anyone is able to answer, I got my server logging to syslog so I could see what happens. The following is displayed when I boot the VM and they're the last logs before the machine comes back up again. 10:00.0/1 is my GPU and 30:00.0 is my USB controller Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered disabled state Dec 22 10:09:43 192.168.0.5 kernel: device vnet0 entered promiscuous mode Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered blocking state Dec 22 10:09:43 192.168.0.5 kernel: br0: port 2(vnet0) entered forwarding state Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003) Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003) Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003) Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: enabling device (0000 -> 0003) Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:10:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002) Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002) Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002) Dec 22 10:09:45 192.168.0.5 kernel: vfio-pci 0000:30:00.4: enabling device (0000 -> 0002)

Hi all, hope you are well. I recently purchased a UPS for my UnRAID server and this morning decide to plug it in. I shut down the server and unplugged it from the 8-gang extension cable it was previously plugged in to. I booted the server and everything seemed OK, so I started up the VM I use for work (it has a GTX1050ti attached). The server froze completely after starting the VM and wouldn't come back up without turning off the power and booting up again. When the server came back up the "Enable VMs" setting in VMManger was set to "No". I re-enabled this and tried again. I have now tried everything I can think of. The machine is plugged in to the original 8-way extension and everything is as it was, but VMs still won't boot. I've removed the VM and recreated it. It boots with no devices passed through. Setting the primary display to VNC but still attaching the GPU makes it crash also. Does anyone have any ideas what could be the cause?

So my issue is sorted. For reasons unknown my Asus router was silently dropping the HTTP challenges. I turned the firewall off and the certs renewed, turned it back on again and all is well. Thanks for your help aptalca!

Yes. Also, when NGINX is up the site https://letsdebug.net/ reports everything is fine, this is not the case using letsencrypt I'm reading your responses to previous posts, you say that nginx isn't running until it get's a cert so what is supposed to be providing the HTTP response?

Hi guys, I'm having issues with this container. I have my domain set up, it has been for a while since this was working until I changed one of the subdomains so it had to re-generate the certificate. The validation fails using http challenge. I have tried removing the container and appdata and even that does not rectify the issue. If I fire up an NGINX container with the default config then it shows the NGINX startup page by going to the domain. When I use this container with the same port forwarding there doesn't seem to be anything listening. This is my log: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Europe/London URL=johimself.co.uk SUBDOMAINS=www, EXTRA_DOMAINS= ONLY_SUBDOMAINS=false DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=MY_EMAIL_ADDRESS STAGING=true NOTICE: Staging is active 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Sub-domains processed are: -d www.johimself.co.uk E-mail address entered: MY_EMAIL_ADDRESS http validation is selected Generating new certificate /usr/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="? if x is 0 or x is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="? if x is 0 or x is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="? elif y is 0 or y is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="? elif y is 0 or y is 1: /usr/lib/python3.8/site-packages/jmespath/visitor.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="? if original_result is 0: Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for www.johimself.co.uk http-01 challenge for johimself.co.uk Waiting for verification... Challenge failed for domain www.johimself.co.uk Challenge failed for domain johimself.co.uk http-01 challenge for www.johimself.co.uk http-01 challenge for johimself.co.uk Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: www.johimself.co.uk Type: connection Detail: During secondary validation: Fetching http://www.johimself.co.uk/.well-known/acme-challenge/Ugsgna0D4LoyVydrpfn93WbNKBjWP2I__LsX0MvbpYQ: Timeout during connect (likely firewall problem) Domain: johimself.co.uk Type: connection Detail: Fetching http://johimself.co.uk/.well-known/acme-challenge/fN_EX6RO0s1Q0u4dNpBURbECXtBVTU6PT1RsDnkxpQs: 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. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: www.johimself.co.uk Type: connection Detail: During secondary validation: Fetching http://www.johimself.co.uk/.well-known/acme-challenge/Ugsgna0D4LoyVydrpfn93WbNKBjWP2I__LsX0MvbpYQ: Timeout during connect (likely firewall problem) Domain: johimself.co.uk Type: connection Detail: Fetching http://johimself.co.uk/.well-known/acme-challenge/fN_EX6RO0s1Q0u4dNpBURbECXtBVTU6PT1RsDnkxpQs: 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. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container If anyone has any more ideas, that would be great!