This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[5.103] Content could not be loaded.

Get error message- Content could not be loaded
Please check the spelling of your URL.
Make sure that your proxy settings are in order.
The following lines may provide some additional information to the cause of the failure.
An error was encountered while scanning the content. Please try again later. If the problem persists please contact your system administrator. HTTP Proxy set to transparent, CF and AV on. The failure is intermittent. Turned off proxy and could see error page flash by and then the requested content. Turned off CF and it works. Turned off AV and left CF on, proxy appears to work.

This thread was automatically locked due to age.

Parents

0 ECKEROTH over 21 years ago

Same problem here. After 5.103 installation i got this error, not everytime but sometimes [:(]
Cancel
Vote Up 0 Vote Down

Cancel
0 bbb_01 over 21 years ago in reply to ECKEROTH

Hi,

i can confirm this behaviour aswell.

I am wondering why this happens when a "Bind Vulnerability" got fixed and "Reporting interface graphs missing"
got fixed.

The customers fear of Vulnerabilities, and are glad to see the Interface graphs again...they install the Up2date, and after that their Webaccess is buggy ? ...nice.... !!

It would be good to have a Up2date Rollback feature, so the customers would have a way to go back without reinstalling.

B
Cancel
Vote Up 0 Vote Down

Cancel
0 alasc over 21 years ago in reply to bbb_01

I have this issue, too!

Very strange!
I´m awaiting an update.

Alex
Cancel
Vote Up 0 Vote Down

Cancel
0 Vukasin over 21 years ago in reply to alasc

could you post the settings you use for pattern updates?
Cancel
Vote Up 0 Vote Down

Cancel
0 efortune over 21 years ago in reply to Vukasin

Pattern Up2date is set for automatically, every hour.
Cancel
Vote Up 0 Vote Down

Cancel
0 efortune over 21 years ago in reply to efortune

The problem appears to coincide with the AV pattern update. It will clear by itself eventually.
Cancel
Vote Up 0 Vote Down

Cancel
0 Vukasin over 21 years ago in reply to efortune

the problem was identified and solved. it will be released in the next up2date. i will post more details in the morning.

thanks to everyone for posting your info and helping us deal with this as soon as possible.
Cancel
Vote Up 0 Vote Down

Cancel
0 FN-Eagle over 21 years ago in reply to Vukasin

I’ve seen these problems several times now. It seems that Astaro is not testing the updates carefully. It is very frustrating if you have a lot of customers with the same problem after a software upgrade. It is even more critical if you do not have the possibility to role it back.
I’ll personally wait and watch the Bulletin Board a while before starting the upgrade. Unfortunately it is not always possible, especially when they role out security fixes.
Cancel
Vote Up 0 Vote Down

Cancel
0 ECKEROTH over 21 years ago in reply to Vukasin

[ QUOTE ]
the problem was identified and solved. it will be released in the next up2date. i will post more details in the morning.

[/ QUOTE ]

When can we expect to hear from you Vukasin?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 ECKEROTH over 21 years ago in reply to Vukasin

[ QUOTE ]
the problem was identified and solved. it will be released in the next up2date. i will post more details in the morning.

[/ QUOTE ]

When can we expect to hear from you Vukasin?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Vukasin over 21 years ago in reply to ECKEROTH

the problem is related to the restart of the virus scanner caused byt pattern updates. the scanner interrupts all current connections (even the innactive ones) which causes failures while scanning (hence the error pages). we are currently testing the solution and will release it as soon as we are sure that nothing else will become broken as a result.
Cancel
Vote Up 0 Vote Down

Cancel
0 Keith_M over 21 years ago in reply to Vukasin

As recommended I changed the virus updates to only run once a day. This has temporarily solved my problem
Cancel
Vote Up 0 Vote Down

Cancel