This has been my understanding of the problem all along. Or I think I was under the impression that you were viewing your website from a browser on the server itself.

Sorry, I have no new ideas at this time.

well, i've routed the traffic through the public ip address for now until i can figure this out. kinda defeats the purpose of a closed circuit system, but it will work for now. i appreciate all of your help.

---
ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net

Re: website issues with 127.0.0.1
By: SYS64738 to echicken on Fri Nov 22 2024 01:25 am

This has been my understanding of the problem all along. Or I think I was under the impression that you were viewing your website from a browser on the server itself.

Sorry, I have no new ideas at this time.

well, i've routed the traffic through the public ip address for now until

i
can figure this out. kinda defeats the purpose of a closed circuit system, but it will work for now. i appreciate all of your help.

well you are doing something out of the ordinary, so you can expect to have issues. we also don't know what you could possibly have done wrong. i've seen it 100 times. people say they dont do anything special and then it ends up being operator error.

the synchornet web isn't even that good or worth using. you can find another solution. i'm not sure what you're trying to do with your closed system. if you have multiple people and want to view the msg bases you can use forum software that polls the msgs via nntp. i did that with 2 softwares.

if it's just for using the bbs, throw up a ftelnet script or whatever.
look around and find your solution. sometimes the only person who can help you is you, because you're the guy behind the wheel.

---
þ Synchronet þ ::: BBSES.info - free BBS services :::

well you are doing something out of the ordinary, so you can expect to have issues. we also don't know what you could possibly have done wrong. i've seen it 100 times. people say they dont do anything special and then it ends up being operator error.

Well, I'm certain it has nothing to do with Synchronet. I copied the whole thing to a new server and had the same issue.

look around and find your solution. sometimes the only person who can help you is you, because you're the guy behind the wheel.

Well, I'm beginning to think that is the case. It's weird to have an issue that you can't see where anyone has discussed it before. I'm sure someone else has had this problem, but for the life of me I can't find where they discussed it at all.

Not sure if this makes any difference at all, but 127.0.0.1 and my locally assigned ip (192.168.0.1) bother produce the same result. Part of me suspects that it has something to do with the router. I dunno. Back to the drawing board.

---
ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net

SYS64738 wrote to MRO <=-

look around and find your solution. sometimes the only person who can help you is you, because you're the guy behind the wheel.

Well, I'm beginning to think that is the case. It's weird to have an issue that you can't see where anyone has discussed it before. I'm
sure someone else has had this problem, but for the life of me I can't find where they discussed it at all.

Not sure if this makes any difference at all, but 127.0.0.1 and my
locally assigned ip (192.168.0.1) bother produce the same result. Part

That's because those addresses are the same thing in reality. They both
point to the local machine.

of me suspects that it has something to do with the router. I dunno.
Back to the drawing board.

It almost certainly does have something to do with the router. Google
up the term "hairpinning" as it relates to routers.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Re: Re: website issues with 127.0.0.1
By: Gamgee to SYS64738 on Sat Nov 23 2024 08:23 am

Not sure if this makes any difference at all, but 127.0.0.1 and my locally assigned ip (192.168.0.1) bother produce the same result. Part

That's because those addresses are the same thing in reality. They both point to the local machine.

Not necessarily. 192.168.* just means "private address" (as in private network), does not mean "localhost" as 127.* does.
--
digital man (rob)

Rush quote #38:
See how it sings like a sad heart, then joyously screams out its pain
Norco, CA WX: 61.8øF, 51.0% humidity, 4 mph W wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Digital Man wrote to Gamgee <=-

Re: Re: website issues with 127.0.0.1
By: Gamgee to SYS64738 on Sat Nov 23 2024 08:23 am

Not sure if this makes any difference at all, but 127.0.0.1 and my locally assigned ip (192.168.0.1) bother produce the same result. Part

That's because those addresses are the same thing in reality. They both point to the local machine.

Not necessarily. 192.168.* just means "private address" (as in private network), does not mean "localhost" as 127.* does.

Certainly true, from a technical perspective, but I believe he's saying
the 192... address is the "locally assigned" IP for his BBS machine, so
at least in this context/example, they're pointing to the same place.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

That's because those addresses are the same thing in reality. They both point to the local machine.

Yes, I believe in essence that the locally assigned 192. points to 127.0.0.1.

It almost certainly does have something to do with the router. Google
up the term "hairpinning" as it relates to routers.

I think you're right. I've had issues with hairpinning in the past, but with different results. Thanks for the advice.

---
ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net