when I run production.yml, I can't connect from the local PC, please help

[josephsvk]

I'm a newbie. everything works from a device outside the home network, I connect normally to the site, but when I connect from a local PC, it connects me. but as long as I test local.yml, everything is fine in the local network. when I tried to run traceroute -> my dns > my public ip -> but an error occurred when connecting to the server. if I try to connect outside the network, everything is fine.

[foarsitter]

Try chatgpt sometime:

Loopback or Hairpin NAT: If you're trying to access the service using its public IP address from within the local network, some routers/firewalls might not support this by default. You may need to enable loopback or hairpin NAT (Network Address Translation) on your router/firewall to allow internal devices to access the service using the public IP address.

Threw in your question and it gives a nice response but I think above quote is the problem.

It sounds like you're experiencing issues accessing a website or service hosted on a local network from within the same network, but it works fine when accessed from outside the network. This could be due to several reasons:

1. DNS Resolution: Ensure that your local DNS server is configured correctly to resolve the domain name to the internal IP address when queried from within the local network. Sometimes, DNS resolution might not work as expected within the local network, causing connection issues.

2. Firewall or Router Configuration: Check your firewall or router settings to ensure that they are not blocking the connection between devices within the local network. Make sure that the necessary ports are open for communication between devices.

3. Loopback or Hairpin NAT: If you're trying to access the service using its public IP address from within the local network, some routers/firewalls might not support this by default. You may need to enable loopback or hairpin NAT (Network Address Translation) on your router/firewall to allow internal devices to access the service using the public IP address.

4. Local Hosts File: Check the local hosts file on your PC to see if there are any entries overriding the DNS resolution for the domain name in question. Incorrect entries in the hosts file can lead to connection issues.

5. Service Configuration: Ensure that the service you're trying to access is configured to accept connections from devices within the local network. Sometimes services are configured to only accept connections from specific IP ranges or interfaces.

6. Network Segmentation: If your local network is segmented into different subnets or VLANs, ensure that proper routing and access controls are in place to allow communication between devices in different segments.

7. IP Address Conflict: Make sure there are no IP address conflicts within your local network. Conflicting IP addresses can disrupt communication between devices.

8. Check Network Devices: Verify the status and configuration of all network devices involved, such as switches, access points, and routers, to ensure they are functioning correctly and not causing any issues.

By troubleshooting these potential issues, you should be able to diagnose and resolve the connectivity problem within your local network. If the issue persists, you may need to provide more specific details about your network setup for further assistance.