Like i said works fine on my laptop ¯\_(ツ)_/¯ all of the links are there and it renders fine.
I'm running Win7 on my home PC, and the browser is Chrome - Version 89.0.4389.114 (Official Build) (64-bit)... and I see no images.
I fired up old unused IE 11... and I can see the images! But I'm not going to use this ancient browser.
What's the solution? Is it up to Cliff Pennock to make his image server play well with Chrome, or is there some setting in Chrome that needs to be tweaked?
So Vivaldi is what i'm using and it just complains but shows the files. If I open MS Edge i see no images unless i disable this site setting "Insecure content" well move it from Block to allow. This is probably the same setting in chrome (as edge is now just a chrome knockoff) and you can set it per site. This may be the work around until Cliff figures it out.
Edit: Also I think somehow browsers are recognizing that "https://images.fiero.nl" is part of fiero.nl and for some reason they are deciding to enforce internal mixed content but not external mixed content.
[This message has been edited by skywurz (edited 04-01-2021).]
If I open MS Edge i see no images unless i disable this site setting "Insecure content" well move it from Block to allow. This is probably the same setting in chrome (as edge is now just a chrome knockoff) and you can set it per site.
I don't know where to find this (or anything similar to it). I'll have to wait until a Chrome brainiac comes along and posts how to do it.
This is because the image host is still working fine its just the client (your browser) deciding to load the image from the host or not. If Cliff adds HTTPS to the image host it may not solve the issue. He may also have to do a find and replace on the forum database for https://images.fiero.nl/userimages and replace it with https://images.fieroforum.com/userimages .
No worky. I can't seem to find the right setting in chrome.
Did you click on the lock symbol to the left of the URL window in Chrome? (It'll say "View site information" if you just hover over it.) Then proceed with the following steps as suggested by skywurz.
quote
Originally posted by Patrick:
I allowedInsecure content in Site settings for this particular site... and now the images show up again.
[This message has been edited by Patrick (edited 04-01-2021).]
PFF Img servers can have problems. PFF Itself causes odd problems For Years because missing data in every page and all browsers have to guess how to format them. Example: Is why you get "illegal character" symbol on some posts. Why? PFF is/was written in HTML4 but missing data saying so and new browsers try to format HTML5 w/ UTF-8 character map.
Then add Browsers want all sites to be Encrypted... The https: Cliff is just making the switch to https: for the forums but now everything is a mixed of https: and http: and many current browsers Hate this. Notice Lock w/ ⚠️ in FF etc....
quote
Originally posted by skywurz: This is because the image host is still working fine its just the client (your browser) deciding to load the image from the host or not. If Cliff adds HTTPS to the image host it may not solve the issue. He may also have to do a find and replace on the forum database for https://images.fiero.nl/userimages and replace it with https://images.fieroforum.com/userimages .
Just Img for PFF alone is 2 or more servers. Then add all other img hosting causing problems.
Would need to update PFF page templates and change all servers to run https Yup... even img above is http not https Many PIP images are on Host Kansas and may not be under CP control.
So yes, Even after CP finish the https switch many can still have problems. Many Browser Authors expect to kill all access to http soon making more problems...
HTTPS... "They" claim to make safer web... https needs Encryption Keys controlled by very few. That few can easily lock out anyone they don't like and far worse then Twitter and other killed Trump accounts. "They" claim a lot of crap for IPv6 too. Now Comcast and others can see Everything behind your local home router and control access too because v6 doesn't allow NAT so you can't hind them. Recently Comcast have quietly leaked will not only control DL and UL speeds and use Data Capping too but soon also limit to X devices for a Teir of Service. So 200/5mbps 1tb cap + 5-7 devices max too. If people are dump enough to have Comcast and other ISP own routers then can make device count to include old things too that normally "hidden" by NAT. Many newer SOHO routers you buy no longer give you an option to disable IPv6 either. Along same lines, Google FF and others blocking Cookies doesn't = you get privacy. Just means Other and Worse ways they track you now and doesn't care what you do to the browser. And using VPN won't stop this either no matter what lies VPN companies claim.
------------------ Dr. Ian Malcolm: Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should. (Jurassic Park)
Modern browsers no longer display mixed content (http and https resources) This, I'm afraid is the natural progression of things as security is constantly tightened. It's obnoxious, but necessary.
Got mine to work using instructions stated above. What's weird is it just happened to not load images anymore after working for a long time. Did something change? I apologize in advance if this was already talked about but I missed it.
Yes, something has changed. PFF is now using a secured connection (https) but the images are still coming from a non-secured domain (images.fieroforum.com) causing some browsers to not willing to displaying them. I'm working on this, but since fieroforum.com and fiero.nl share the same IP address, it's not a simple task to solve..
Ok, images should be visible again (for those who had problems) and browsers should no longer complain about parts of the page being insecure.
But I expect problems when people link to (non-https) images outside of the PFF servers. Unfortunately, I have no control over that.
The switch to https was necessary. Not only for security but because the almighty Google penalizes sites that are insecure. When searching for "fiero", PFF dropped in the search results from the #1 spot to... well, no idea where to since PFF didn't show up in the results at all.
It's odd that Google ignores the largest Fiero site in the world. But I hope that's going to change now.
Ok, images should be visible again (for those who had problems) and browsers should no longer complain about parts of the page being insecure.
But I expect problems when people link to (non-https) images outside of the PFF servers. Unfortunately, I have no control over that.
The switch to https was necessary. Not only for security but because the almighty Google penalizes sites that are insecure. When searching for "fiero", PFF dropped in the search results from the #1 spot to... well, no idea where to since PFF didn't show up in the results at all.
It's odd that Google ignores the largest Fiero site in the world. But I hope that's going to change now.
Great work! Thanks Cliff!
[This message has been edited by skywurz (edited 04-03-2021).]
But I'm not going to use this ancient browser.
I allowed Insecure content in Site settings for this particular site... and now the images show up again. Thanks. 
https needs Encryption Keys controlled by very few. That few can easily lock out anyone they don't like and far worse then Twitter and other killed Trump accounts.
