Jump to content

Stuck in downloading bin.pigg


Recommended Posts

Need a little help...

Upon updating my Macbook pro client, Island Rum is stuck at at downloading bin.pigg

 

been like that for hours now.

 

Same scenario with my Dell xps laptop...  Tequila is stuck in downloading bin.pigg

 

Investigating further, I checked out the Manifest file https://patch.savecoh.com/manifest.xml and it loaded fine.

 

the items in the filelist timed out i.e.

http://cdn-na1.homecomingservers.com/hc/assets/20210426_4294/patch/bin.pigg

 

however if you hcange protocol to https, it will resolve properly.\ i.e.

https://cdn-na1.homecomingservers.com/hc/assets/20210426_4294/patch/bin.pigg

 

 

I'm not really sure how everything is put together here... But any help/clarification/directions would be greatly appreciated.

 

maybe if the manifest wasn't published correctly? like http vs https... just a guess

 

 

 

Screen Shot 2021-04-28 at 4.53.16 AM.png

Link to post
Share on other sites

sounding like you might not be alone.

 

HC folks will jump on it. It might be something simple.

"Homecoming is not perfect but it is still better than the alternative.. at least so far" - Unknown  (Wise words Unknown!)

 

Sooo.. I guess I am taking a non-voluntary break until November?!

 

Si vis pacem, para bellum

Link to post
Share on other sites
3 minutes ago, Faultline said:

Both links point to the same place and are working; do you have a firewall/antivirus that may be blocking Island Rum?

 

Nope... no firewall/antivirus here.

 

The http url example I gave above came from the manifest my client is trying to load.  It does not load for me ( probably why it is stuck in bin.pigg - trying to load that via http).  However if I try to access that resource via https, it will resolve and allow me to download that file directly (There a lot of files to go through that manifest list so doing that one by one manually might not be the smartest thing lol). 

 

Although if you say both links work for you... and only one works for me, this may be an ISP routing/caching thing that I may not have any control over... 

 

14 minutes ago, Troo said:

sounding like you might not be alone.

 

HC folks will jump on it. It might be something simple.

 

Hopefully its just a simple configuration on my end... cross fingers       

 

Link to post
Share on other sites
  • Developer

I just changed the manifests to use https instead of http, see if that solves the issue for you. It is not ideal for downloads that don't need to be secured because the https handshake makes the download start slower, but it'll help if you have anything in the route that is intercepting unencrypted http and messing with it.

  • Thanks 2
Link to post
Share on other sites
2 minutes ago, Faultline said:

I just changed the manifests to use https instead of http, see if that solves the issue for you. It is not ideal for downloads that don't need to be secured because the https handshake makes the download start slower, but it'll help if you have anything in the route that is intercepting unencrypted http and messing with it.

 

Whoa.. it worked! thank you... Thank you very much!  And thanks for taking the time. 

 

 

Link to post
Share on other sites
8 minutes ago, Faultline said:

I just changed the manifests to use https instead of http, see if that solves the issue for you. It is not ideal for downloads that don't need to be secured because the https handshake makes the download start slower, but it'll help if you have anything in the route that is intercepting unencrypted http and messing with it.

Also just an added FYI, My Dell laptop client is also updating now.  Looks like the http vs https really was the culprit.  I do understand your dilemma though, coz I as a dev, I would prefer the plain http protocol for downloading stuff as it is faster.  This looks like an ISP thing on my end though. 

 

Thanks Faultline. You rock! 

Link to post
Share on other sites
  • Homecoming Team

You're not the only one, someone else I helped on discord had trouble with one specific file (stage3e.pigg) stalling out over http, no matter if they tried to download it from the North America mirrors or the EU one. They could get it over https so I chalked it up to a malfunctioning ISP caching proxy or security scanner.

 

Fortunately it was only the one file and they were able to get it manually over https. The new launcher does fail back to https, but for a stuck transfer like that it may take quite some time for it to give up on the http version. May have to flip the defaults for a while.

  • Thanks 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...