1:04 pm, August 21, 2014
26,791
Resolved Glyph update error #5 and Rift update error #1016
Hi Folks,
I had posted a while back about the Glyph client being unable to update itself in this thread:
http://forums.riftgame.com/technical...-http-0-a.html
As a workaround, I had to manually download Glyph every time it got updated -- which was as frequently as once a day or once a week. That was annoying, but workable.
Then, a few days ago I started getting errors after logging into Glyph, when it checks to see whether Rift needs to be updated. It was reporting error #1016.
I couldn't find any information on this by looking through the forums and googling it.
I thought maybe one of the IP addresses that Glyph/Rift communicate with might have changed and I needed to add it to my firewall exclusion list. I added a few new ones that were getting blocked, but that didn't solve the issue.
Then I looked at the logs in C:\users\<username>\appdata\local\Glyph\logs. It indicated that it was using the "cURL" utility to retrieve the current Rift version file, but was unable to and reported a cURL error #5. I looked this up in the cURL library documentation and found that it means that cURL couldn't resolve the proxy server.
I was able to retrieve the version file manually in my browser, so I dug a little deeper into how cURL decided whether or not to use a proxy. It turns out that I had an environment variable set for http_proxy. The proxy host I had set there is only accessible if I am VPN'd in to my company's network -- which I am not if I am playing RIft. I deleted that environment variable, and voila, it solved both issues. It seems both Glyph updater and Rift updater use cURL and were being affected by that environment variable.
I hope this helps someone, because it stumped me for a good while.
Cheers,
Aumentar
I had posted a while back about the Glyph client being unable to update itself in this thread:
http://forums.riftgame.com/technical...-http-0-a.html
As a workaround, I had to manually download Glyph every time it got updated -- which was as frequently as once a day or once a week. That was annoying, but workable.
Then, a few days ago I started getting errors after logging into Glyph, when it checks to see whether Rift needs to be updated. It was reporting error #1016.
I couldn't find any information on this by looking through the forums and googling it.
I thought maybe one of the IP addresses that Glyph/Rift communicate with might have changed and I needed to add it to my firewall exclusion list. I added a few new ones that were getting blocked, but that didn't solve the issue.
Then I looked at the logs in C:\users\<username>\appdata\local\Glyph\logs. It indicated that it was using the "cURL" utility to retrieve the current Rift version file, but was unable to and reported a cURL error #5. I looked this up in the cURL library documentation and found that it means that cURL couldn't resolve the proxy server.
I was able to retrieve the version file manually in my browser, so I dug a little deeper into how cURL decided whether or not to use a proxy. It turns out that I had an environment variable set for http_proxy. The proxy host I had set there is only accessible if I am VPN'd in to my company's network -- which I am not if I am playing RIft. I deleted that environment variable, and voila, it solved both issues. It seems both Glyph updater and Rift updater use cURL and were being affected by that environment variable.
I hope this helps someone, because it stumped me for a good while.
Cheers,
Aumentar
References
Guest 2:47 am, January 27, 2015 4
Can you please explain how to do this for people who aren't very good with computers? This is the only actual answer I have found to fix error# 1016 but I'm very confused with what you actually did to solve the problem. Thank you
Like [4]
Reply
