Відео

You probably have to bridge or set the network interface on the LXC to ‘bridge’. You would be basically bridging it with the network interface of the machine the Proxmox server is running. Sorry for my rambling 🙏

@@brigadierwilliamwildebeest1112 thank you sir for your quick reply but I did it and take help also chat gpt but not success. If you can help please.

@@debnathmriganka2010no worries. On the LXC, did you configure the gateway address to be the same as the address the Proxmox server is using as a gateway to the Internet?

@@brigadierwilliamwildebeest1112 yes sir, I can share my all screenshot to you if give me your contact or I also can share my screen also.

note for anyone else that came across this issue - I was using staging acme, i changed it over to production caServer in traefik/data/traefik.yml file and remove everything in acme.json --> restarted traefik and waited 20minutes and it resolved the HSTS issue and I can now access my services locally :)

No, if that's the case then you don't require traefik, you can just open the ports required using the ports section in each container's subsection in docker compose. Then you can go to localhost:port to browse the required service, and comment out the traefik labels. But it is recommended to use the services with traefik to have it integrate it later on with services like crowdsec, etc. and for https endpoints.

@@TechnoBoomYT thank you

Mostly yes for using this tutorial, as the docker image is based on custom use with pia vpn. This is also configured for proper port forwarding to the qbittorrent container. You can modify the config to use with other vpn services using the gluetun docker image but mostly you will not get the automatic configuration of vpn provider in case of free vpn provider. Although in any case, if you are using a vpn then your isp can't trace information back to you.

@@TechnoBoomYTright now I use wire guard easy to access my home server when I’m off my local network. I do have surf shark that I use for other purposes. What’s the best option?

You can keep using the wireguard method for accessing the services, just expose the ports required then and comment out or remove the traefik labels in that case. You'll need to expose the ports for all the services in the docker compose file and make sure to expose the port of qbittorrent under the vpn container's docker compose. Also, as i have used the docker vpn image of pia vpn only instead of gluetun, so you'll need to change the docker image to gluetun one instead. If you're using a vpn service that doesn't support port forwarding, then you'll be limiting your peers in downloading and would thus face issues in downloads. As far as i know, surfshark doesn't support port forwarding in the vpn. I hope that gives a better idea about the setup.

@@TechnoBoomYT thanks, do you know a good vpn that allows port forwarding? thanks in advance

You can use VPNs like proton vpn and private internet access vpn, both of which have port forwarding support in gluetun docker vpn. There may be some more choices, so you may explore them also. But these two are the most compatible with the setup.

I'm glad that you liked it. Regarding the issue for iGPU passthrough, you will need to disable the proxmox host from using the iGPU first. For that you will need to modify the grub config to GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt initcall_blacklist=sysfb_init video=simplefb:off video=vesafb:off video=efifb:off video=vesa:off disable_vga=1 vfio_iommu_type1.allow_unsafe_interrupts=1 kvm.ignore_msrs=1 modprobe.blacklist=radeon,nouveau,nvidia,nvidiafb,nvidia-gpu,snd_hda_intel,snd_hda_codec_hdmi,i915" and then run update-grub. This command effectively disables the VGA output to be used by the proxmox host and thus frees up the gpu to be able to be passed through to any VM. After updating the grub config, you will just need to pass through the iGPU to the vm, and then you will be able to access the iGPU stats. Also, I specifically planned to make a separate video for GPU Passthrough due to the sheer amount of configuration required to set up properly in different systems.

Depending on which service the error is present, there may be a misconfiguration in either the docker labels for service name in the router labels or a misconfiguration in the password hash if on traefik dashboard. The services should also be on the same docker network as the traefik reverse proxy. Try to check once again the labels for the services having the issue. It may solve it then. The error 404 is due to the traefik not able to connect to the service. Try pinging the service from inside the traefik container and ensure both should be on the same docker network

You may use the dynamic config of traefik to point to the ip address of the specific machine for other than docker use. 33:46

How about traefik and crowdsec

Tutorial coming soon !

@@TechnoBoomYT thank you so much creating a video please add also a waf for traefik .