Cannot access site

[timnboys]

Please help me I cannot access my website.
when I try to access my website via my webhost's ssl certificate which is here: /https://lithiumhost.com/~keyedin/updates/versioninfo_weather4U.xml
Please help me because I cannot get my software to update without having this accessible.
Because when someone tries to access it I get this in my cpanel error log on my account:

Mon May 06 13:49:00 2013] [error] [client *Censured*] Caught race condition abuser. attacker: 502, victim: 509 open file owner: 509, open file: /home/keyedin/public_html/updates/versioninfo_weather4U.xml

Please help me.

 

[Infopro]

Can't help with your software, but I would guess it'll work better with FQDN.

This isn't: /~keyedin/

 

[timnboys]

So that wasn't my cpanel shared ssl link?
My cpanel shows this is my shared ssl url:

So how do you think I can access my shared ssl link
without getting the error described below:

[Thu May 09 09:46:49 2013] [error] [client 204.49.244.2] Caught race condition abuser. attacker: 502, victim: 509 open file owner: 509, open file: /home/keyedin/public_html/index.html, referer: https://keyedinsoft1.tk:2083/{censured}/frontend/x3/ssl/index.html

Please help me with this error.
Actually I am not looking for help with my software, I am just looking for help in fixing the race condition abuser error when I try to access my website.

 

[JaredR.]

Have you asked your hosting provider for help with this?

 

[timnboys]

Have you asked your hosting provider for help with this?

I have and they still won't answer me or help me.
Please could you help me with this error?

 

[JaredR.]

Are you trying to use symlinks on your site? The first result in a Google search for "Caught race condition abuser" is this:

Symlink Race Condition Protection

Remember that no one in this forum has access to your site or to your host's servers. If your site is using symlinks, or if your account somehow has symlinks pointing to another location, and your host has applied the patch mentioned in that link, that would explain what is happening.

Only your host has the access needed to conclusively find the cause of this problem, however. You really need to get your host to help you. No one in this forum has the access needed to investigate your exact situation on your host's server.