there's no place like 127.0.0.1

[Floki]

Get it?

 

[Magyars]

Had to look it up....... interesting....
Clever. In a nerdy, technical way.

 

[Gaffer]

Yeah being in IT :>)...

I like this one also:

There are 10 types of people in this world, those who understand binary and those who don't!

 

[fullmetaljesus]

There's no place like "loop back"?
That doesn't seem right.

 

[snapping turtle]

58008 on a Ti-30 calculator turned upside down spells boobs.

 

[OurDee]

Sounds like he lives between 5 and 7.

 

[jamil]

There's no place like "loop back"?
That doesn't seem right.

I was gonna say, there's no place like localhost? But technically you beat me to it.

 

[Expat]

Not in IT, but started running Linux around 98 or so. And you had to know about that sort of thing before it started going down the automagical path.

 

[druckernut]

Get it?

Yeah, but what happens if I sail [to] 127.0.0.1 and port 80 is blocked and I cannot dock. What's a person to do?

 

[Airtevron1]

Yeah, but what happens if I sail [to] 127.0.0.1 and port 80 is blocked and I cannot dock. What's a person to do?

Open on the firewall...

 

[DoggyDaddy]

I have no idea what's going on.

 

[DoggyDaddy]

I didn't know if it was an IP address or GPS coordinates.

 

[rhamersley]

I didn't know if it was an IP address or GPS coordinates.

Neither, it’s his briefcase combination…

 

[WebSnyper]

Someone looking for me?

 

[Expat]

Yeah, but what happens if I sail [to] 127.0.0.1 and port 80 is blocked and I cannot dock. What's a person to do?

In the old days you would finger some other ports

 

[jkaetz]

I prefer ::1 myself.

 

[idkfa]

Here's a real conundrum for all y'all IT-inclined.
I have an app running on port 9000 on one Windows 10 machine (let's call its IP PC1).
I have another Win 10 machine on the same network (PC2).

1) I can ping PC1 from PC2
2) I can

telnet PC1 9000

from PC2
3) I can

nc -v PC1 9000

from PC2's WSL2 instance
4) PROBLEM: I cannot PC1:9000 in the browser on PC2
5)

curl PC1:9000

returns

url: (56) Recv failure: Connection was reset

Cherry on the top: I was able to access the app from any machine on LAN.
The problem started when I recently moved and connected to ATT fiber, so I had to set up their POS modem/router as a passthrough.


So it's
- not the firewall,
- not the antivirus,
- not the app.

Out of ideas.

 

[KellyinAvon]

Neither, it’s his briefcase combination…

That's 1-2-3-4-5

 

[BigRed]

Here's a real conundrum for all y'all IT-inclined.
I have an app running on port 9000 on one Windows 10 machine (let's call its IP PC1).
I have another Win 10 machine on the same network (PC2).

1) I can ping PC1 from PC2
2) I can

telnet PC1 9000

from PC2
3) I can

nc -v PC1 9000

from PC2's WSL2 instance
4) PROBLEM: I cannot PC1:9000 in the browser on PC2
5)

curl PC1:9000

returns

url: (56) Recv failure: Connection was reset

Cherry on the top: I was able to access the app from any machine on LAN.
The problem started when I recently moved and connected to ATT fiber, so I had to set up their POS modem/router as a passthrough.


So it's
- not the firewall,
- not the antivirus,
- not the app.

Out of ideas.

Did you try rebooting your machine?

 

[jkaetz]

Here's a real conundrum for all y'all IT-inclined.
I have an app running on port 9000 on one Windows 10 machine (let's call its IP PC1).
I have another Win 10 machine on the same network (PC2).

1) I can ping PC1 from PC2
2) I can

telnet PC1 9000

from PC2
3) I can

nc -v PC1 9000

from PC2's WSL2 instance
4) PROBLEM: I cannot PC1:9000 in the browser on PC2
5)

curl PC1:9000

returns

url: (56) Recv failure: Connection was reset

Cherry on the top: I was able to access the app from any machine on LAN.
The problem started when I recently moved and connected to ATT fiber, so I had to set up their POS modem/router as a passthrough.


So it's
- not the firewall,
- not the antivirus,
- not the app.

Out of ideas.

You said passthrough, presumably with your router. Are both systems on your router?

Assuming yes, are you using ip address or DNS names to connect?