Then why'd you reply in the first place? :)
I specifically mentioned Proxmon (even without the additional capitcal M) as a third party android app in the main post. So I assumed that would wave the confusion.
So I've noticed something odd. I've set up a user with custom permissions, and the Web GUI works just fine alongside custom domain on desktop. Even Proxmon (the third party app) works fine. But when using the official app, I keep getting "API ERROR - 403: Forbidden".
Origin is set to...
So after some time, I finally got proxmox to work. I can access the GUI and it has a network/internet connection just fine using the following:
However, having issues with containers having no internet access. Currently a test container has the following info:
arch: amd64
cores: 2
cpulimit...
Thanks for the reply.
Loading kernel module index.
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Found container virtualization none.
Using default interface naming scheme 'v252'.
Parsed configuration file "/usr/lib/systemd/network/99-default.link"
Parsed configuration file...
Got it to (semi) work.. finally..
So setting up the enp35s0 (using iface enp35s0 inet static) doesn't work, but like this does? While I can access the proxmox GUI.. can't seem to ping anything/apt update. Yet... Oddly enough it seems it can't access the outside, yet I can access the GUI O_o.
Well, through KVM it works fine:
interfaces settings I use atm:
Using this due to: https://github.com/ariadata/proxmox-hetzner
I used to have enp35s0 set to static with the address / gateway there:
auto lo
iface lo inet loopback
iface lo inet6 loopback
auto enp35s0
iface enp35s0 inet...
Kinda gave up using the iso installer. The installation worked flawlessly on my auction dedicated AMD server, but after reboots the server was just not reachable.
I had this set up:
auto enp35s0
iface enp35s0 inet static
address mainip
netmask 255.255.255.192
gateway gateway
up route...
What I currently have in my network interfaces is NAT forwarding 80/443 to my reverse proxy container. My entire server is only having a single IP address. Now while that is working great, the main problem is due to the NAT forwarding the firewall rules (on the host & container) are useless when...
Greetings.
As of a long time, I noticed that only root user has access to update the system on the main node. Even though I created a user with full admin access the 'upgrade' option is gray, and only refresh is available. Any reason as to why this is?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.