In Russia, your site is not accessible at all. But both panoramas open without problems through VPN through the United States and Great Britain (without losing tiles)

Yes, I tested it on several services

I'm loosing tiles... I'd say this is a server problem.

maybe you can fix it by adding :


(default is 2)

https://krpano.com/docu/xml/#network

ps. cool panorama photos !

--- EDIT ---

i get even flickering tiles... really strange...
and i got this for one panorama

Forbidden
You don't have permission to access this resource.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

reload and it worked again...

Looks like the server is forbidding the request for some reason. I thought maybe your file upload was interrupted and didn't finish, but the server is displaying a 403 error which means it knows the file is there but refuses to send it. I might try to upload again and overwrite the existing files. Or you might need to talk to the host. Maybe a load limit issue?

I see this from Australia (krpano version). These are the only two tiles missing in all the 360s.

Chrome
Windows 10

Hope that helps.

Hi,

this is very clearly a server issue - after a several loading requests your server starts blocking some request. Maybe it is overloaded or has a limit of requests/second or so.

Please contact your hoster for more information!

That happens in your krpano AND in your pano2vr example, see in the networks tab in the browsers developer tools for files with status 403.

But krpano retries failed downloads only 2 times by default.
As can be seen in the network tab, pano2vr also retries failed downloads, but more often (I don't know how often by default).

So as already commended above add this line anywhere in your xml, maybe even with a higher number:

Then krpano will retried the downloads more often and it will work.

E.g. here your tour with retrycount=99 (set as url parameter):
https://virtualvisitr.com/panoramas/Dail…k.retrycount=99

But a note about that - that will be more like a workaround, normally a (good) server shouldn't act like this. E.g. your server could also fails at the initial html page load and then you will got an error anyway.

The real and only correct solution would be contacting your hoster for solving that problem (like removing some limits or upgrading the server).

Best regards,
Klaus