When I try to access my webpage from 127.0.0.1 (localhost), I get this contorted-looking webpage and can't figure out why. Any ideas?
Re: website issues with 127.0.0.1
By: SYS64738 to All on Fri Oct 04 2024 09:55:20
The browser is failing to load certain resources, like the stylesheet and probably some javascript. I don't know why this is happening. As far as I can remember, your hostname isn't baked into these URLs and the paths are relative, so it should work.
It's possible that this stuff is loading but some script is crashing and breaking the page.
It's possible that you have some mixed HTTP / HTTPS thing going on, or there's something about your setup we don't know about (edits to index.xjs, a reverse proxy in front, etc.).
I could say more if I could see the network requests and errors in your browser's dev tools, and look at the source of the broken page, but I can't do that from here.
Are you using Firefox? This is how mine looks when using Firefox. All other browsers display fine for my site.
https://a-net-online.lol * A-Net Online
Re: website issues with 127.0.0.1
By: SYS64738 to All on Fri Oct 04 2024 09:55:20
The browser is failing to load certain resources, like the stylesheet and probably some javascript. I don't know why this is happening. As far as I can remember, your hostname isn't baked into these URLs and the paths are relative, so it should work.
It's possible that this stuff is loading but some script is crashing and breaking the page.
It's possible that you have some mixed HTTP / HTTPS thing going on, or there's something about your setup we don't know about (edits to index.xjs, a reverse proxy in front, etc.).
I could say more if I could see the network requests and errors in your browser's dev tools, and look at the source of the broken page, but I can't do that from here.
Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH | bootstrap.min.css:1 +
Failed to load resource: net::ERR_TIMED_OUT | checkbox.css:1
Failed to load resource: net::ERR_TIMED_OUT | offcanvas.css:1
Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH | bootstrap.min.js:1 +
Re: website issues with 127.0.0.1
By: SYS64738 to echicken on Sat Oct 05 2024 02:46:34
Something very wonky going on with your webserver and/or your connection to it.
This isn't a webv4 problem in itself; the Synchronet webserver sends these files to your browser without the help of any script I wrote.
I'll ponder it and let you know if I think of anything. Especially weird that this only happens within localhost, if I'm understanding correctly. I'm sure that's telling of something but I don't know what.
I use Chrome and Firefox. I get the same result on both. Yours looks fine to me as well.
Here's a list of the errors I encountered when pulling up the localhost in my browser:
Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH | bootstrap.min.css:1 +
I use Chrome and Firefox. I get the same result on both. Yours looks fine
to me as well.
looks normal on chrome.
i dont use foxfire.
Re: website issues with 127.0.0.1
By: MRO to SYS64738 on Sat Oct 05 2024 09:33 pm
I use Chrome and Firefox. I get the same result on both. Yours looks f
to me as well.
looks normal on chrome.
i dont use foxfire.
What's Foxfire? Did you mean Firefox?
Re: website issues with 127.0.0.1
By: SYS64738 to echicken on Sat Oct 05 2024 02:46 am
how about using your domain instead?
---
� Synchronet � ::: BBSES.info - free BBS services :::
Re: website issues with 127.0.0.1
By: SYS64738 to echicken on Sat Oct 05 2024 02:46:34
Something very wonky going on with your webserver and/or your connection to it.
This isn't a webv4 problem in itself; the Synchronet webserver sends these files to your browser without the help of any script I wrote.
I'll ponder it and let you know if I think of anything. Especially weird that this only happens within localhost, if I'm understanding correctly. I'm sure that's telling of something but I don't know what.
So, I found someone having a similar problem on a tomcat server that found
In conf/server.xml config file in apache tomcat folder set the "usesendfile" attribute to "false" as shown below:-
I'm thinking that if I could find the equivalent file/variable to edit in sbbs, then this could possibly work for me also. What do you think?
We don't have an equivalent that I'm aware of. Are you seeing errors related to content length mismatch in your browser's dev tools? You may have the same symptoms as this person, but there are many possible causes.
Since this only happens to you within the confines of your server, you could try adding an entry to your server's hosts file. Have it so that geo.synchro.net points to 127.0.0.1. Then try loading the page again. If that fixes it, that would mean webv4 is building one or more URLs incorrectly. This shouldn't be the case and it's something I avoided, but worth checking.
I'm an old school programmer, so please forgive my ignorance, but I assume that there is some sort of "CHECK"
Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH |
that there is some sort of "CHECK" (old school term, sorry) going on as a security check (?). Which makes me ask 1) why? and 2) who the &^*$ cares,
I seriously don't think it is something that sbbs' webserver is doing.
Yeah, I doubt it as well, if only because I haven't heard of this before from anyone else. But I also haven't tried viewing my website from the server itself recently if ever, so I don't know.
That's the thing I keep scratching my head about. It seems to me that if it was happening when accessing via localhost, then the same should happen when accessing via my public ip address...shouldn't it?
I'm still curious to know what happens if you put an entry for geo.synchro.net in your server's hosts file, map it to 127.0.0.1, and then visit geo.synchro.net from a browser on the server. If that works, it's a workaround and telling of something.
I'd be interested to see the actual response to one of these failed requests with the content length mismatch. If you click on one of them in the browser's dev console, you should see some tabs for Headers and Response among others. It'd be interesting to know if the bad response for bootstrap.min.css for example still looks like a CSS file, if the browser shows anything there.
I tried that and got the contorted-looking home page like this: https://imgur.com/qsT1fL6
I'm running into some new-to-me territory, but I think I have what you are asking about. I got this from the web developer controls debugger in Firefox: https://pastebin.com/2dmvQkKJ
I'm assuming you opened the inspector / dev tools, went to the network tab, and selected one of the requests that had a content-length mismatch error, and this is what was in the "response" (raw) area off to the right.
What was the URL for this request? The actual response here is the output of index.xjs, or the home/default page of your site. If the request was not for '/' or for 'index.xjs' then we'll need to find out why your server sent this.
I made an interesting discovery. This contorted website seemingly occurs only if I try to access my local IP address from the host device on my local network. For instance, I'm accessing the website from my phone right now through my local IP address with no issues. Everything looks normal.
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.
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.
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.
look around and find your solution. sometimes the only person who can help you is you, because you're the guy behind the wheel.
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
of me suspects that it has something to do with the router. I dunno.
Back to the drawing board.
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.
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.
That's because those addresses are the same thing in reality. They both point to the local machine.
It almost certainly does have something to do with the router. Google
up the term "hairpinning" as it relates to routers.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,068 |
| Nodes: | 17 (1 / 16) |
| Uptime: | 20:54:11 |
| Calls: | 501,140 |
| Calls today: | 12 |
| Files: | 109,394 |
| D/L today: |
2,980 files (692M bytes) |
| Messages: | 300,730 |