Site Issues?

[rmc523]

I think I’ve brought this up before but can’t find it nor do I remember if there was any resolution….

I’ve had this issue on multiple browsers on the computer and now phone….the site becomes completely illegible, and can’t log in or do anything really. I can sort of read between massive gaps of blank space and it’s difficult, but not much else. I had just relegated myself to using the phone (as I thought it was something with the desktop version of the site), but now my phone is doing it too
i downloaded a new browser on the phone and it seems to be working like normal here but who knows for how long.
I've cleared browser cache, history etc, and that doesn’t seem to do anything. To fix the issue

I can try to provide screenshots if needed….is anyone else having this issue, and did y’all figure out how to fix this?

thanks in advance…

[Nick]

I have the same thing happen to me. Although, right at this moment the site's working fine on my PC. Seems completely random as to when I have the issue and when I don't.

[rmc523]

I have the same thing happen to me. Although, right at this moment the site's working fine on my PC. Seems completely random as to when I have the issue and when I don't.

strange, my desktop version has been that ways for months and never went back.

[Nick]

strange, my desktop version has been that ways for months and never went back.

I've been dealing with it for years. It always seems to work on my phone, but different PCs it;s a crapshoot.

[fish16]

I forgot what I did exactly but it’s something in the security settings for this website

[rmc523]

Anyone from site admin able to chime in?

[Nick]

Anyone from site admin able to chime in?

Yeah there ain't really a site admin. Basically, I let mk7 know when the site goes down and he calls up some dude to get it back up, and that's the extent of the adminning done. lol

[rmc523]

Yeah there ain't really a site admin. Basically, I let mk7 know when the site goes down and he calls up some dude to get it back up, and that's the extent of the adminning done. lol

I didn’t really think so (figured it was one of the regulars)….ok shrug lol. I’ll just ride this browser until it glitches too haha

[Nick]

Update: The site is hosed on my PC again.

[dgriot]

Pretty much all browsers, unless it's an old enough version, default to blocking mixed content.

When you fire up https://soflamarlins.com, it comes back with the initial webpage that looks jank. In that webpage, there're also requests to grab JavaScript files, CSS, etc. hosted at soflamarlins.com so it looks as expected. But those links are setup as:

http://soflamarlins.com/js/login.js
http://soflamarlins.com/js/header-rollup-563.js
http://soflamarlins.com/css.php
etc.

Those http:// links aren't loaded when you've already established a https connection (requests back and forth between your browser and the server are encrypted based on the https certificate), and asking for regular http requests at that point is a potential Man in the Middle security risk.

So, the fix on the server side would be updating all the links to https:// instead of http://

The "fix" on the client side (i.e., "I trust this site, I'm good with it reaching for stuff over http despite being https") is to go into settings on your browser and allow for insecure content for soflamarlins.com.

For Chrome, you'd click the icon right next to the URL --> Site Settings --> Choose Allow for Insecure Content

Should be very similar for other browsers, just search for allow insecure content <browser name>.

[Nick]

Pretty much all browsers, unless it's an old enough version, default to blocking mixed content.

When you fire up https://soflamarlins.com, it comes back with the initial webpage that looks jank. In that webpage, there're also requests to grab JavaScript files, CSS, etc. hosted at soflamarlins.com so it looks as expected. But those links are setup as:

http://soflamarlins.com/js/login.js
http://soflamarlins.com/js/header-rollup-563.js
http://soflamarlins.com/css.php
etc.

Those http:// links aren't loaded when you've already established a https connection (requests back and forth between your browser and the server are encrypted based on the https certificate), and asking for regular http requests at that point is a potential Man in the Middle security risk.

So, the fix on the server side would be updating all the links to https:// instead of http://

The "fix" on the client side (i.e., "I trust this site, I'm good with it reaching for stuff over http despite being https") is to go into settings on your browser and allow for insecure content for soflamarlins.com.

For Chrome, you'd click the icon right next to the URL --> Site Settings --> Choose Allow for Insecure Content

Should be very similar for other browsers, just search for allow insecure content <browser name>.

Thanks man, it fixed it for me. Haha, been dealing with it for years, and the fix was that simple.