• website issues with 127.0.0.1

    From SYS64738@VERT/GEO to All on Fri Oct 4 09:55:20 2024
    Hello, all!

    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?

    https://imgur.com/qsT1fL6

    Here's how it is supposed to look:

    https://imgur.com/agCIDFy

    I've searched but haven't found anything that could address this particular issue.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From echicken@VERT/ECBBS to SYS64738 on Fri Oct 4 12:57:11 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to All on Fri Oct 04 2024 09:55:20

    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?

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From StingRay@VERT/ANETO to SYS64738 on Fri Oct 4 16:59:03 2024
    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

    -StingRay

    ---
    þ Synchronet þ ANETO
  • From SYS64738@VERT/GEO to echicken on Sat Oct 5 01:43:52 2024
    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 did make a couple of edits on index.xjs. I'll reset it to the original and see if that makes a difference.

    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.

    I'll check out the dev tools also and see if it throws up any red flags.

    Thanks, echicken!

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From SYS64738@VERT/GEO to StingRay on Sat Oct 5 01:45:56 2024
    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

    I use Chrome and Firefox. I get the same result on both. Yours looks fine to me as well.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From SYS64738@VERT/GEO to echicken on Sat Oct 5 02:46:34 2024
    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.

    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 +

    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 +

    Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH | jquery.min.js:1 +

    Uncaught Reference Error: $ is not defined at (index):9:4 | (index):9

    Uncaught Reference Error: $ is not defined at offcanvas.js:1:1 | offcanvas.js:1

    Uncaught Reference Error: $ is not defined at (index):255:4 | (index):255

    Uncaught Reference Error: $ is not defined at HTML Document.<anonymous> (common.js:135:2) | common.js:135

    Uncaught Reference Error: $ is not defined at window.onload (common.js:154:2) | common.js:154

    Uncaught Reference Error: $ is not defined at (index):139:5 | (index):139

    A screenshot for the errors can be seen here: https://imgur.com/n6bKbtg

    Resetting the index.xjs file had no affect on the errors, btw.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From echicken@VERT/ECBBS to SYS64738 on Sat Oct 5 12:13:09 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to echicken on Sat Oct 05 2024 02:46:34

    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 +

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From SYS64738@VERT/GEO to echicken on Sat Oct 5 21:13:16 2024
    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.

    Ok. I appreciate you. I'll keep poking and prodding around and if I discover anything, then I will let you know as well.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From MRO@VERT/BBSESINF to SYS64738 on Sat Oct 5 21:33:48 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to StingRay on Sat Oct 05 2024 01:45 am


    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.
    ---
    þ Synchronet þ ::: BBSES.info - free BBS services :::
  • From MRO@VERT/BBSESINF to SYS64738 on Sat Oct 5 21:34:21 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to echicken on Sat Oct 05 2024 02:46 am


    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 +

    how about using your domain instead?
    ---
    þ Synchronet þ ::: BBSES.info - free BBS services :::
  • From Nightfox@VERT/DIGDIST to MRO on Sat Oct 5 22:28:54 2024
    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 fine
    to me as well.

    looks normal on chrome.
    i dont use foxfire.

    What's Foxfire? Did you mean Firefox?

    Nightfox

    ---
    þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
  • From mro@VERT to Nightfox on Sun Oct 6 16:29:28 2024
    To: Nightfox
    Re: website issues with 127.0.0.1
    By: Nightfox to MRO on Sat Oct 05 2024 10:28 pm

    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?

    i call it foxfire because all the old people i know who use it call it that. --- Synchronet 3.19b-Win32 NewsLink 1.113
    * Data Stream - dsbbs.net - telnet://dsbbs.net
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From SYS64738@VERT/GEO to MRO on Tue Oct 8 02:59:09 2024
    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 :::

    This is on a private internal network.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From SYS64738@VERT/GEO to echicken on Fri Oct 18 10:07:57 2024
    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 a solution. Below are some copy/pastes from the forum where I found this:

    In conf/server.xml config file in apache tomcat folder set the "usesendfile" attribute to "false" as shown below:-

    <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" **useSendfile="false"**/>

    The entire discuss can be seen here: https://stackoverflow.com/questions/260130 15/err-content-length-mismatch-while-loading-js-files-on-tomcat-server. 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?

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From echicken@VERT/ECBBS to SYS64738 on Fri Oct 18 19:18:52 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to echicken on Fri Oct 18 2024 10:07:57

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From SYS64738@VERT/GEO to echicken on Sun Oct 20 22:13:57 2024
    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.

    Yes, I'm getting the following length content errors, among others:

    Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH | bootstrap.min.css:1 +

    Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH | bootstrap.min.js:1 +

    Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH | jquery.min.js:1 +

    I'm an old school programmer, so please forgive my ignorance, but I assume 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, just display it!

    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 seriously don't think it is something that sbbs' webserver is doing. Mainly because I've seen the same type set up on other machines, and they wouldn't have this issue. However, what you have suggested might be at least good for troubleshooting so I don't have to wonder if that's going on. I'll check it out.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From SYS64738@VERT/GEO to echicken on Sun Oct 20 22:15:58 2024
    I'm an old school programmer, so please forgive my ignorance, but I assume that there is some sort of "CHECK"

    sorry, i meant to say "CHECKSUM".

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From echicken@VERT/ECBBS to SYS64738 on Sun Oct 20 23:46:49 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to echicken on Sun Oct 20 2024 22:13:57

    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 believe this is part of the HTTP spec, and for a client (eg. browser) to be RFC compliant it must behave this way.

    It's an indication of corruption. The response header (from the server) said the body would be n bytes long, but the client received a body of different size. I guess they decided it's better to discard such responses than to proceed as if everything were normal, since there's a good chance something will go wrong when further processing takes place.

    I suppose there could be security implications, but if something's tampering with the body, why not the headers as well.

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From SYS64738@VERT/GEO to echicken on Mon Oct 28 01:49:47 2024
    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?

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From echicken@VERT/ECBBS to SYS64738 on Mon Oct 28 14:27:31 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to echicken on Mon Oct 28 2024 01:49:47

    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?

    All things being equal, sure, but there are a ton of little things that could be happening.

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From SYS64738@VERT/GEO to echicken on Tue Oct 29 02:53:04 2024
    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 tried that and got the contorted-looking home page like this: https://imgur.com/qsT1fL6

    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'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

    If that's not what you were looking for, then I can go back and try to find it.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From echicken@VERT/ECBBS to SYS64738 on Tue Oct 29 16:56:27 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to echicken on Tue Oct 29 2024 02:53:04

    I tried that and got the contorted-looking home page like this: https://imgur.com/qsT1fL6

    Same as with using localhost as the address then, so we can probably rule out a hostname-related problem.

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From SYS64738@VERT/GEO to echicken on Mon Nov 4 22:18:58 2024
    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.

    The URL was https://127.0.0.1 and below is the output for one of the errors if I am understanding correctly.

    https://pastebin.com/xaHWNnTw

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From SYS64738@VERT/GEO to echicken on Tue Nov 5 15:47:48 2024
    Same as with using localhost as the address then, so we can probably rule out a hostname-related problem.

    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.

    I'm eager to hear your thoughts on this.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From echicken@VERT/ECBBS to SYS64738 on Wed Nov 6 00:01:06 2024
    Re: website issues with 127.0.0.1
    By: SYS64738 to echicken on Tue Nov 05 2024 15:47:48

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From SYS64738@VERT/GEO to echicken on Wed Nov 6 02:03:49 2024
    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.

    I'm thinking that since this is a problem that occurs only on the host machine, then I should be good to go. I'll put it through the paces and find out.

    ---
    ï¿­ Synchronet ï¿­ GeoSync - geo.synchro.net
  • From SYS64738@VERT/GEO to echicken on Fri Nov 22 01:25:23 2024
    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
  • From MRO@VERT/BBSESINF to SYS64738 on Fri Nov 22 12:06:24 2024
    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 :::
  • From SYS64738@VERT/GEO to MRO on Fri Nov 22 20:43:35 2024
    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