Issue accessing specific website


#1

Hello we are having an issue with one specific local machine.

This machine accesses the site www.mlpp.org however it doesn’t have a valid certificate and therefore pulls up an out of date version of the web page. We have tried this with google chrome, firefox, and edge and get the same results. We have tried different wireless and wired networks and get the same results, meanwhile other computers pull up the website just fine.

We have also tried to import the security certificate from a computer that works and that also has not worked for us.

Wondering if you may have any insight for us before we rebuilt the computer.


#2

Hi @yflit

I can’t see a problem ( https://check-your-website.server-daten.de/?q=mlpp.org ). The page has a Grade B, this is good (only missing HSTS header).

Opend with FireFox, there are some blocked scripts.

Laden von gemischten aktiven Inhalten "http://s7.addthis.com/js/250/addthis_widget.js?ver=4.9.9" wurde blockiert.[Weitere Informationen] mlpp.org
JQMIGRATE: Migrate is installed, version 1.4.1 jquery-migrate.min.js:2:542
Laden von gemischten aktiven Inhalten "http://s7.addthis.com/js/250/addthis_widget.js?ver=4.9.9" wurde blockiert.[Weitere Informationen] mlpp.org
Laden fehlgeschlagen für das <script> mit der Quelle "http://s7.addthis.com/js/250/addthis_widget.js?ver=4.9.9". mlpp.org:65:1
Laden fehlgeschlagen für das <script> mit der Quelle "https://connect.facebook.net/en_US/fbevents.js". mlpp.org:1:1
23423 core-scripts.6.1.4.js:13:1
Laden fehlgeschlagen für das <script> mit der Quelle "https://cdn.jsdelivr.net/wp/wp-slimstat/tags/4.7.8.3/wp-slimstat.min.js". mlpp.org:1684:1
ready for rock

Same with Chrome. It’s curious, Chrome has also blocked mixed content, but the content is blocked, so

org

is the result, no warnings. I don’t see an ipv6, so it’s not an ipv6-problem.

Edit: Perhaps there is a caching instance that shows old content.


#3

Tried to clear browser cache and reinstalled browsers still, nothing. Will rebuild and hopefully it fixes.


#4

Maybe the client machine has an /etc/hosts or hosts.txt file that hardcodes a particular IP address for this server?


#5

Yep that was it, it seems that when they were changing web providers there was a temporary fix that hardcoded their IP address here and once that was removed we could access the correct site. Thanks!


closed #6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.