nginx IPv6 configuration #158

New Issue

2022-01-02T02:41:57+01:00

dxgldotorg commented

2022-01-02 02:41:57 +01:00

(Migrated from github.com)

Upon attempting to connect to Mainsail Chrome returned a Connection Refused error. Looking at the open ports in netstat I saw that ports 80 and 81 were bound to the IPv4 0.0.0.0 but not to the IPv6 :: address. Checked the nginx configuration files and it only had the listen 80 on the mainsail config and listen 81 on the fluidd config.

Describe the solution you'd like

Add to the nginx config files the following:
For the mainsail config file add after the first listen directive:
listen [::]:80 ipv6only=on;

For the fluidd config file add again after the first listen directive:
listen [::]:81 ipv6only=on;

Port numbers should of course be substituted if KIAUH is configured with alternate ports.

Describe alternatives you've considered

No response

Additional information

No response

### Is your feature request related to a problem? Please describe Upon attempting to connect to Mainsail Chrome returned a Connection Refused error. Looking at the open ports in netstat I saw that ports 80 and 81 were bound to the IPv4 0.0.0.0 but not to the IPv6 :: address. Checked the nginx configuration files and it only had the listen 80 on the mainsail config and listen 81 on the fluidd config. ### Describe the solution you'd like Add to the nginx config files the following: For the mainsail config file add after the first listen directive: `listen [::]:80 ipv6only=on;` For the fluidd config file add again after the first listen directive: `listen [::]:81 ipv6only=on;` Port numbers should of course be substituted if KIAUH is configured with alternate ports. ### Describe alternatives you've considered _No response_ ### Additional information _No response_

dw-0 commented

2022-01-03 10:13:03 +01:00

(Migrated from github.com)

Yes, i think i can re-add that.
Regarding to the NGINX docs, that ipv6only=on flag isn't needed, because it seems to be on by default: https://nginx.org/en/docs/http/ngx_http_core_module.html#listen

Yes, i think i can re-add that. Regarding to the NGINX docs, that `ipv6only=on` flag isn't needed, because it seems to be on by default: https://nginx.org/en/docs/http/ngx_http_core_module.html#listen

dxgldotorg commented

2022-01-09 00:12:54 +01:00

(Migrated from github.com)

I just found out it was causing connection errors between mainsail and moonraker due to it not detecting being in a trusted IP range. Made it stop listening on IPv6 and the problem went away. Apparently my connection errors may have been due to my router not advertising the IPv4 properly.

dw-0 commented

2022-01-09 09:55:54 +01:00

(Migrated from github.com)

But did you add the correct ipv6 address to the trusted clients in the moonraker.conf? That's necessary of course...

dxgldotorg commented

2022-01-11 02:23:09 +01:00

(Migrated from github.com)

Since my IPv6 addresses are derived from my ISP address and thus subject to change I just removed the IPv6 support once again from the nginx config. Only the v4 addresses are truly static on my network.

dw-0 commented

2022-01-11 08:49:33 +01:00

(Migrated from github.com)

Okay, i think i will revert that change and remove the IPV6 line again. There were no real issues the whole time and in this case i didn't knew it will in turn cause for some unexpected trouble.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: h3n3/kiauh#158