-
Cannot reach my domain name after changing ISP to PPPoE
My new ISP was blocking the port 80 and 443. That was the explication. Thx for the support.
-
Cannot reach my domain name after changing ISP to PPPoE
@Kilrah Thx for the reply and I don't think so because the traceroute reach my public IP address and Duckdns have the corret IPv4 (no IPv6) by subdomain. So the DNS is update to the correct IP. @BRiT Thx you too for your suggestion.
-
Cannot reach my domain name after changing ISP to PPPoE
I don't think so. Hairpin is similar to Loopback if I'm right. And it permit to access services via the public IP address or domain name from inside the local network. Another PC on my LAN can't reach Nextcloud (for exemple) with his domain name but it works with his IP address. I can reach my domain name service from the inside of my lan with the VM too. My problem is the impossibility to reach my service via domain name from the oustide of my LAN. I think the Hairpin/Loopback problem is part of the symptom, not the solution. Is that right?
-
-
Cannot reach my domain name after changing ISP to PPPoE
Hello unraid community, Recently, I've changed my Internet Service Provider. My last modem/router was in bridge mode with a personal router behind. That was working well. All the port forwarding was in my personal router. My new ISP allow me to use my personal router with PPPoE (MTU 1492) WAN connection. So now my router have a public IP and I didn't made any change in the firewall or the port forwarding router config. All the PCs/Smartphones/VM have internet and work well. Unraid is reachable from internet with the myserver plugin, plex work well too. I can update doker/apps/etc... from unraid. But I can't reach my domain name from duckdns (example.duckdns.org). If I Ping it from WAN, it's not reachable. But a traceroute from WAN reach my correct public IP. I can reach my domain name from a Windows VM in my unraid server. I can reach my domain name from any device in my LAN but not from the WAN. But I can PING or traceroute my domain name from WAN, it's my correct public IP address. So if I'm right: My proxy manager Nginx work, Duckdns work and have my correct IP address. Where's the problem? Do you have any suggestion? Thx for reading me. mydeedee-diagnostics-20220731-0143.zip
-
Error 43 - GPU Passthrough - Bare metal Win 10 Pro uefi boot - Nvidia GTX 1060 6G - unraid 6.10.2
Thx a lot ghost82, I've allowed unsafe interrupt and after an update with "Geforce Experience", it finally works.
-
Error 43 - GPU Passthrough - Bare metal Win 10 Pro uefi boot - Nvidia GTX 1060 6G - unraid 6.10.2
Hello ghost82, thanks for the answer. I've attached the full diagnostics. This should be the symptom that the gpu is in use by the host. Sorry for my lack of knowledge, but how can I find if the GPU is in use by the host and how can I fix it? mydeedee-diagnostics-20220604-2007.zip
-
Error 43 - GPU Passthrough - Bare metal Win 10 Pro uefi boot - Nvidia GTX 1060 6G - unraid 6.10.2
Hello guys, I have got a MSI GTX 1060 6g that I want to passthrough with bare metal Win 10 Pro. Wathever I've tried, the graphic card returned the error 43. Win 10 works fine. I've already follow this threads without success: I've looked for some common problem and don't worked for me: - I've looked for some virtualization problem in my BIOS. - I've tried Q35 or i440fx machine. - I've tried to disable Hyper-V - I've followed the SpaceInvaderOne tutorial for GPU passthrough and edited my XML. - I've tried dumping my vbios with SpaceInvaderOne script but it crashes with the 6.10.x unraid version. So I've tried to use a working Vbios I've allready done and tested. Any help will be appreciated 🙂 VM WIN10Pro.txt Logs.txt
-
WIN 10 VM \Boot\BCD I/O error after unraid 6.10.1 update
Thanks a lot ghost82. Replacing the seabios was the solution, I've reach Windows with VNC. I hope seabios will be update soon in unraid stable distro. Well done
-
WIN 10 VM \Boot\BCD I/O error after unraid 6.10.1 update
The VM boot on this screen (screenshot attached) who last for less than one second. And than it show the Boot\BCD error screen. I've tried ESC/ ctrl+alt+del/ F2 etc.. nothing change. No boot option. Is there a trick that I don't know?
-
WIN 10 VM \Boot\BCD I/O error after unraid 6.10.1 update
Thank you ghost82. Yeah it's a legacy install so I use Seabios. I've already try ovmf. Are there less problems with UEFI install? I can't change it for know but just in case. I'm considerating downgrade unraid because I need this VM to work now.
-
WIN 10 VM \Boot\BCD I/O error after unraid 6.10.1 update
Hello everyone, I'm having a bad experience right now. My baremetal Win 10 Pro won't boot with Qemu after unraid 6.10.1 upgrade. Win boot work correctely when I launch it directly from my NVME. This is the error into VNC: I hope someone can help me. I've tried to create new template without success. I've tried to delete the libvirt.img. And I've already tried black Voodoo stuff like start/stop VM/server etc... Windows 10 Qemu.txt
HerrGeneral
Members
-
Joined
-
Last visited