[GH-ISSUE #581] Connecting to localhost issue: WARN dead loop detected #471

New issue

Open

opened 2026-02-27 23:17:00 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 23:17:00 +03:00

Owner

Originally created by @0x0OZ on GitHub (Mar 6, 2025).
Original GitHub issue: https://github.com/snail007/goproxy/issues/581

When trying to access the ip 127.0.0.1 or a hostname resolving to it, I get the warning

I tried running goproxy as socks proxy and HTTP proxy..

Not sure if that's bug related to firefox or the tool itself

Originally created by @0x0OZ on GitHub (Mar 6, 2025). Original GitHub issue: https://github.com/snail007/goproxy/issues/581 When trying to access the ip 127.0.0.1 or a hostname resolving to it, I get the warning ![Image](https://github.com/user-attachments/assets/444dcc65-b0c7-418b-b7a8-ba88d6b14c05) I tried running goproxy as socks proxy and HTTP proxy.. Not sure if that's bug related to firefox or the tool itself

kerem commented

2026-02-27 23:17:01 +03:00

Author

Owner

@snail007 commented on GitHub (Mar 6, 2025):

the domain format must be a normal one, must contains the dot.

@snail007 commented on GitHub (Mar 6, 2025): the domain format must be a normal one, must contains the dot.

kerem commented

2026-02-27 23:17:01 +03:00

Author

Owner

@0x0OZ commented on GitHub (Mar 7, 2025):

Okay! I wonder why, but thanks. The issue was resolved when using a dotted domain.

@0x0OZ commented on GitHub (Mar 7, 2025): Okay! I wonder why, but thanks. The issue was resolved when using a dotted domain.

kerem commented

2026-02-27 23:17:01 +03:00

Author

Owner

@0x0OZ commented on GitHub (Mar 11, 2025):

Okay so I haven't noticed until now, but when the proxy resolves this fake local domain, it doesn't try to connect to localhost but rather to the interface IP.

So I have an app that is being hosted on localhost not 127.0.0.1 and if I try to connect to the virtual domain e.g oz.oz which is resolving to 127.0.0.1
To connect to that host, I need to try to access localhost not 127.0.0.1

Is there a way to go around this?

@0x0OZ commented on GitHub (Mar 11, 2025): Okay so I haven't noticed until now, but when the proxy resolves this fake local domain, it doesn't try to connect to localhost but rather to the interface IP. So I have an app that is being hosted on `localhost` not `127.0.0.1` and if I try to connect to the virtual domain e.g `oz.oz` which is resolving to `127.0.0.1` To connect to that host, I need to try to access `localhost` not `127.0.0.1` ![Image](https://github.com/user-attachments/assets/eae3d048-0bfb-41fe-b9ed-db4279a3ce99) Is there a way to go around this?