|
|
Post by Slanger on Mar 10, 2021 16:32:05 GMT
Hi,
I've been getting an "Error 999" message on our league site for a couple of months. Users from across the country on different ISP's, platforms, browsers, etc are all getting the error, though not all the time. Usually refreshing once or twice displays the page. This happens on the main index, and on both .html and .php pages (it is not exclusive to any add on or single page). There seem to be some times when it happens 75% of the time you click a link, then sometimes it works fine for a day, only to return the next.
We've done everything recommended on the error message, and I called Yahoo tech support for help, but they basically read back the same thing to me. They have no idea what is causing it.
I am a rookie coder, and I put together a new homepage (my first real attempt) for our league last summer. It was running fine until around mid-January. I did not change anything beyond basic images and text on the homepage. The homepage itself started having issues with displaying images (not all of them loading) and the structure being somewhat jumbled. As I said I am a novice at this so it could be something really obvious I have missed. Would appreciate some insight from more knowledgeable people 
|
|
|
|
Post by eleclerc on Mar 10, 2021 22:27:12 GMT
|
|
|
|
Post by Slanger on Mar 10, 2021 22:34:51 GMT
OK thanks a lot, no real rush.
It doesn't sound like the reason listed on the page you linked, regarding the amount of traffic. Basically just 20 guys using it, me (commish) by far the most, but it's happening across the board with everyone. The site was stable for years with times of much higher traffic. And no one's been locked out for even close to 2 hrs, it's usually fixed with 1-3 refreshes.
|
|
|
|
Post by eleclerc on Mar 11, 2021 11:45:10 GMT
If I look at Google Chrome console, there is no major error.
Just one minor error easy to correct :
Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Arimo&subset=latin,cyrillic,latin-ext'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Arimo&subset=latin,cyrillic,latin-ext'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Arimo&subset=latin,cyrillic,latin-ext'. This request has been blocked; the content must be served over HTTPS.
In all your style.css change : http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext
by : https://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext
You have to do the correction for all googleapis.com links.
Let's see if the page doesn't bug after that...
Also, the 999 never showed to me.
|
|
|
|
Post by Slanger on Mar 11, 2021 15:56:23 GMT
OK thank you Eric, I appreciate you taking the time. I fixed the .css addresses, the fonts are displaying properly now  . I also had some links on the index file linked with 'http' instead of 'https' so that might have been a factor.
Interesting that you don't get the error. There seem to be times when it is worse than others. I've asked for more feedback from the league so I will keep let you know if anything changes.
|
|
|
|
Post by eleclerc on Mar 11, 2021 21:31:12 GMT
If you want some hints like, how to center things in the main index, I can provide you some...
|
|
|
|
Post by Slanger on Mar 11, 2021 22:22:46 GMT
If you want some hints like, how to center things in the main index, I can provide you some... Haha yeah I am still new at this - I got some stuff centred but not all 
So at first changing the addresses to https seemed to fix it for a while, but it's been happening again a bit. Might be time to find a new server.
|
|
|
|
Post by eleclerc on Mar 12, 2021 0:06:12 GMT
I have to delete my temporary files in order to display the last css files. Still showing the errors before that. This is normal, because web browser like Chrome, it keeps the files for 30 days by default.
Changing server, maybe, this is the ultimate solution. But, if I'm your position, I will try to talk to someone at Yahoo (support).
|
|
|
|
Post by Slanger on Mar 21, 2021 21:25:33 GMT
I have to delete my temporary files in order to display the last css files. Still showing the errors before that. This is normal, because web browser like Chrome, it keeps the files for 30 days by default. Changing server, maybe, this is the ultimate solution. But, if I'm your position, I will try to talk to someone at Yahoo (support). So the error has been better, but there are times when the page will just not load fully (images and backgrounds missing) or not load at all (error 999). I've changed all the http addresses to https.
This seems to be the case with all users, sometimes you get no errors for hours and smooth loading, sometimes every click has a problem and you get images/backgrounds not loading.
Yahoo support is very little help, they basically read me what their FAQ says. One thing they said might be an issue is at the user end, if there are multiple devices on the same line it can cause partial loading or the error 999 message.
I don't know if it's at Yahoo's end or not, but another server might be in the cards.
(I've managed to get things centred, btw!)
|
|
|
|
Post by eleclerc on Mar 21, 2021 22:48:36 GMT
Good job to align center the content. Some errors are gone, some are staying, just missed. Here some hints about them. 1- Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext'. This request has been blocked; the content must be served over HTTPS. 2- www.thecphl.com/:1 Mixed Content: The page at 'https://www.thecphl.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-ext'. This request has been blocked; the content must be served over HTTPS. 3- (index):239 GET www.thecphl.com/menu_files/css3menu5/style.css net::ERR_ABORTED 404 (Not Found) Remaining three errors from google console. 1. https://www.thecphl.com/menu_files/css3menu4/style.csslinks font to: http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-extChange http for https 2. https://www.thecphl.com/menu_files/css3menu1/style.csslinks font to: http://fonts.googleapis.com/css?family=Alegreya+Sans+SC&subset=latin,latin-extChange http for https 3. <link rel="stylesheet" href="menu_files/css3menu5/style.css" type="text/css" /><style type="text/css">._css3m{display:none}</style>The style.css doesn't loaded because it doesn't exist... just look at your files if there is an error. When all the errors are gone, we can continue to remove html bugs with the online tool: w3c validator. |
|
|
|
Post by Slanger on Mar 22, 2021 0:14:11 GMT
3. <link rel="stylesheet" href="menu_files/css3menu5/style.css" type="text/css" /><style type="text/css">._css3m{display:none}</style>The style.css doesn't loaded because it doesn't exist... just look at your files if there is an error. When all the errors are gone, we can continue to remove html bugs with the online tool: w3c validator.
OK I fixed the first two - menu5 was deleted (but I still had the link to it in the top) so I removed that, so should be good on all 3 of those errors.
|
|
|
|
Post by eleclerc on Mar 22, 2021 10:58:12 GMT
|
|
|
|
Post by Slanger on Mar 22, 2021 15:32:36 GMT
Yeah it does seem to happen more at certain times. Time for a different server.
Regarding the icons, do you mean the team logos in the score ticker? The larger image with the 20 logos on it is just one single image, no urls. I have all 4 of the images on the page linked with the <img src=".....">. Could that be slowing it down?
Thanks for the links - that stuff is way beyond my understanding but I will keep it bookmarked
|
|
|
|
Post by eleclerc on Mar 22, 2021 21:08:19 GMT
It's for the "./images/logos.banner.png". Normally, leagues uses icons to link Team Cards or LinkedRosters.
You can use this big banner as multiple link and multiple image. This is even recommanded by standard, one big image is better than 20 smaller images.
If you want some help in order to do it, I can.
|
|
|
|
Post by Slanger on Mar 23, 2021 16:23:15 GMT
It's for the "./images/logos.banner.png". Normally, leagues uses icons to link Team Cards or LinkedRosters. You can use this big banner as multiple link and multiple image. This is even recommanded by standard, one big image is better than 20 smaller images. If you want some help in order to do it, I can. Yes I have seen that done and also on the w3 Schools tutorials - would love to get something like that up. |
|
. I also had some links on the index file linked with 'http' instead of 'https' so that might have been a factor.