-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to upload crash dump: couldn't connect to host (7) #18
Comments
I ran some tests and this is what I found out: If I run a dedicated server with my build and Accelerator on a local Windows machine and crash it, the crash report is immediately uploaded to crash.limetech.org (I have a static IP: 95.143.216.252). If I run the same build (of course with Linux versions of the same extensions and mods) of the dedicated server on a Linux machine on hosting and crash it there, then the crash report is not uploaded to crash.limetech.org I tried : -condebug, -debug, cURL Extension (1.3.0.0), nothing helps. After the crash and rebooting the dedicated server on hosting I see only one message from Accelerator in the console:
SourceMod errors_20240905.log:
accelerator.log:
Is the problem on my hosting side? |
I contacted the technical support of my hosting, and they told me that connections from their side are ignored by the crash.limetech.org service and I should address this problem to the Accelerator developer. They claim that the problem is not on their side and everything worked stably before. crash.limetech.org ignores connection from IP 46.174.50.10 of my server:
Is it possible to fix this please? |
There are no network-level restrictions on access to crash.limetech.org, unfortunately this problem is with your hosting provider or their ISP. They'll need to do some basic network diagnostics to narrow down the problem, if you'd like my help then I would like at minimum the output of |
I'm also experiencing this problem, and a look at But I don't get an error message after logging on to https://crash.limetech.org So I looked at
There are also a lot of duplicate error messages in
This is the result of my test
This is the result of my test
Does this have anything to do with the sourcemod version? I'm using sm-1.12 version, not sm-1.11.
|
Thank you for your reply and help. I asked the hosting tech support to run this network diagnostic, they replied that the result is as follows:
Hope this helps to find the problem. |
Both your cases look like some sort of intercepting proxy on the outbound connection (which isn't particularly surprising given your hosting locations), could you please both also try Having checked the logs, Throttle isn't seeing the requests that are failing at all, and I've verified there's no firewall configuration on my end that could cause this - the timeouts mean that something is completely dropping packets, but the traceroutes show that ICMP traffic is making it without issue. @SefoNotasi your host's ISP appears to completely block all HTTP traffic to Throttle. @F1F88 your host's ISP appears to only block the presubmit request, which may be something specific to the way it is encoded. |
Last time I created issues - crash logs are not uploading:
#17
Now I have a new error:
accelerator.log
errors_20240903.log
Dedicated server on linux, latest version of Accelerator, IP: 46.174.50.10:27268
The text was updated successfully, but these errors were encountered: