LXC installation fails due to DNS issue with raw.githubusercontent.com

[Hamed Roshan]

Hello,
I am experiencing an issue while installing an LXC container on Proxmox VE.
Environment:
Proxmox VE: 9.1.4
Kernel: 6.17.4-2-pve
Container OS: Debian 13 (unprivileged)
Network: IPv4 working, IPv6 disabled/not used
Problem: The container is created successfully and has IPv4 connectivity, but the installation script fails when trying to access GitHub raw content.
Output excerpt:

IPv4 Internet Connected
Git DNS:
github.com: ✓
api.github.com: ✓
git.community-scripts.org: ✓
raw.githubusercontent.com: ✗

Installation failed (exit code: 130)
The script hangs while accessing raw.githubusercontent.com, leading to a manual interrupt (SIGINT).
Notes:
DNS appears to be the issue, not general connectivity
Public DNS servers (1.1.1.1 / 8.8.8.8) were tested
Other GitHub domains resolve correctly
Question: Is there a recommended Proxmox or LXC DNS configuration to avoid issues accessing raw.githubusercontent.com during automated installations?
Thank you.

 

[aaron]

How are you installing these containers? The output looks a lot like some 3rd party community scripts not provided by Proxmox. So I would ask there why things might be failing. As it could very well be something going wrong there and not on the container side.

 

[Hamed Roshan]

How are you installing these containers? The output looks a lot like some 3rd party community scripts not provided by Proxmox. So I would ask there why things might be failing. As it could very well be something going wrong there and not on the container side.

Thanks for the clarification.
Yes, the containers are being installed using the community helper scripts (MediaMTX LXC), not official Proxmox tools.

I’ve confirmed that the container itself has working IPv4 connectivity and DNS, and the failure consistently occurs when the script tries to access raw.githubusercontent.com, which appears to be blocked or unstable on my network.

Using the official Gitea mirror provided by the community-scripts project resolves the issue, so it does not seem to be a Proxmox or LXC configuration problem.

 

[Impact]

Reproduce the DNS issue with standard linux tools in a manually created debian CT, share pct config CTIDHERE and we can help you.