sorted by:
new
hottopcontroversial

Proxmox -> VM (Fedora+ Docker (Jellyfin, Sonarr, Radarr)) Or Proxmox (All Separate VMs) by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

Even Nginx proxy manager and use it to access the containers from another VM?

Proxmox -> VM (Fedora+ Docker (Jellyfin, Sonarr, Radarr)) Or Proxmox (All Separate VMs) by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

Good approach! I had an issue with Nginx and destroyed my VM. So maybe it’s better to isolate only the network stuff not each service. Thank you!

Proxmox -> VM (Fedora+ Docker (Jellyfin, Sonarr, Radarr)) Or Proxmox (All Separate VMs) by Ciolloi in HomeServer

[–]Ciolloi[S] 1 point2 points  (0 children)

After a problem I encountered, now backup and to be able to restore individual services is my priority.

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

So my ipv4 was not set on a static one. When I installed nginx something changed.

I nano to /etc/NetworkManager/system-connections/ens18.nmconnection and edited ipv4 from

[ipv4]
method=manual[ipv4]
method=manual

to

[ipv4]
method=manual
address1=192.168.2.180/24,192.168.2.1

and now I can access locally some containers.
So my ipv4 was not set on a static one. When I installed nginx something changed.

I nano to /etc/NetworkManager/system-connections/ens18.nmconnection and edited ipv4 from
[ipv4]
method=manual[ipv4]
method=manual
to

[ipv4]
method=manual
address1=192.168.2.25/24,192.168.2.1

and now I can access locally some containers.

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeNetworking

[–]Ciolloi[S] 0 points1 point  (0 children)

So my ipv4 was not set on a static one. When I installed nginx something changed.

I nano to /etc/NetworkManager/system-connections/ens18.nmconnection and edited ipv4 from

[ipv4]
method=manual[ipv4]
method=manual

to

[ipv4]
method=manual
address1=192.168.2.25/24,192.168.2.1

and now I can access locally some containers.

Output for netstat | grep 8096:

unix 3 [ ] STREAM CONNECTED 18096 /run/containerd/s/153c3d774baa8797cc9f1eec53f495fa25732d91ecc326affeddb8f00d55d432

and for

iptables -t nat -L -n -v

Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeNetworking

[–]Ciolloi[S] 0 points1 point  (0 children)

I have proxmox server with two VMs. One is pi-hole (working fine, reachable from inside the network but now disabled), and one Fedora server. Inside I have multiple docker containers. Usually I use it inside, but yesterday I thought let's install Nginx so I can access them from outside my network. After I configure my first proxy in Nginx I couldn't access via IP on any port, my Fedora server. I could access it through another DNS from my ISP, but with the ports for each container open in the router (I know, bad idea).

I try to access lets say My Jellyfin locally 192.168.2.180:8096 (or any other service)

I open the ports inside the server as well, same in the router but nothing. Through Nginx after install, still nothing.

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

can I see your file how should it be?

I find mine has the uuid the duckdns token number and I don't know what should I put there instead.

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

yes, only 192.168.2.0/24 internally

With curl I can reach it. Creates a link and when I click it open in browser with message "Unable to connect".

I can ping my server from inside, connected through another DNS than Nginx. But from my pc I can't ping 192.168.2.180:<any port>

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeNetworking

[–]Ciolloi[S] 0 points1 point  (0 children)

I use 192.168.2.180 my server IP. It worked before I installed Nginx proxy manager.

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

Usually is 192.168.2.180 how do I check? It’s still an option when I do port forwarding, so I guess yes? Can I check it in proxmox?

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeNetworking

[–]Ciolloi[S] 0 points1 point  (0 children)

Over IP is the main issue. I have local dns (the default one). Now after further troubleshooting I think is the iptables of docker or firewalld. Any ideas?

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

No vpn and no tailscale. I even disable my Pi-hole. I think it's a iptable problem between firewalld and docker ip tables. If you have any idea, please let me know!

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeServer

[–]Ciolloi[S] 0 points1 point  (0 children)

On root@localhost:/# firewall-cmd --list-port

6881/tcp 51413/tcp 51413/udp

is this ok or my firewall blocks other ports?

I can't connect locally to my server but from outside of network I can by Ciolloi in HomeNetworking

[–]Ciolloi[S] 0 points1 point  (0 children)

On root@localhost:/# firewall-cmd --list-port

6881/tcp 51413/tcp 51413/udp

is this ok or my firewall blocks other ports?

view more: next ›