Hello,
I don’t get crash reportings anymore. This is similar to Crash reporting stopped working a couple weeks ago - Unity Services - Unity Discussions
Note that as I am using my own client (backported to Unity 4.6/7), I may be subject to changes on your side, like last time.
I was about to make some releases today, but I would prefer to have this feature working.
@ChrisLundquist do you know what could be wrong ?
Hey again Jerome!
You are one of our original users and it looks like “2828145a-*” might be pointing at the original URL of perf.cloud.unity3d.com
For a while we forwarded reports sent to perf.cloud.unity3d.com → perf-events.cloud.unity3d.com
A while back Amazon changed DNS for the (perf-events) load balancer and nginx caches the DNS resolution.
I kicked nginx to make it point to the new DNS, but it looks like it is getting 500s when trying to forward the report.
The only other change we deployed lately was a fix to truncate really long exception messages so they fit in our database.
I kicked nginx again and I’m seeing a few of your reports. It looks like they might have changed DNS on us again.
It seems like if you update the URL to perf-events.cloud.unity3d.com you should be good for a while.
Hope this helps,
Chris Lundquist
Looks like it works. I integrated your change, and kicked out our builds, Will double check them tomorrow and report if something is amiss.
Thanks a lot for the time. Really appreciated.
Hello @ChrisLundquist
I made further tests on another project. ID ADB4C234-… The project is new from today.
The perf-events URL is not working. The perf one is.
Connection refused - connect(2) for “perf-events.cloud.unity3d.com” port 80 (Errno::ECONNREFUSED)
Am I missing something ?
I just shipped a product today after validating last week that the new URL was working well 
Looks like you’re missing the “s”
We only accept crash reports securely 
$ curl http://perf-events.cloud.unity3d.com
curl: (7) Failed to connect to perf-events.cloud.unity3d.com port 80: Connection refused
$ curl https://perf-events.cloud.unity3d.com
{
“Error”: “Resource not found”
}
I’ll see if I can fix the forwarding again for the old URL in the mean time.
Chris Lundquist
Hmm, can you send me that ruby script in a gist and/or email?
I’ve taken my best guess about why Ruby was unhappy with https://perf-events.cloud.unity3d.com/
It may work now that we’re returning 202 accepted in the happy case. Before we didn’t set status and just closed the connection.
If you have that script available I can test using it.
Hope this helps,
Chris Lundquist
