MCS login down for me?

[Taco]

Has anyone else tried logging in to MCS? It has been for at least an hour unless something is just wrong with my security. I can't bid on any of the SA ending tonight. Will they push all the auctions back a day?

[shadroch]

Im logged pon, but its been doing strange things all day. Showing me past results instead of current stuff, ect,ect

[mycomicshop]

I'm seeing certificate revoke errors, which would be due to fixes we put in related to the recent Heartbleed SSL vulnerability. We're checking on it now, and if no immediate fix, I'll bump tonight's auctions back a day.

[Taco]

I'm seeing certificate revoke errors, which would be due to fixed we put in related to the recent Heartbleed SSL vulnerability. We're checking on it now, and if no immediate fix, I'll bump tonight's auctions back a day.

 

Thank you!

[DiceX]

I had the same problem. If I tried to refresh my already logged in browser window it gave an error.

I could go back to previously viewed pages and had the same issue.

 

I tried typing https://www.mycomicshop.com directly in the address bar and it still had errors.

When I took off he https:// and typed in www.mycomicshop.com , it started working again without a problem.

 

It was odd and did it on both of my computers.

 

 

[Cyclops]

I'm seeing certificate revoke errors, which would be due to fixes we put in related to the recent Heartbleed SSL vulnerability. We're checking on it now, and if no immediate fix, I'll bump tonight's auctions back a day.

 

Are there any other security concerns relating to Heartbleed, Conan? Was MCS compromised at all?

[mycomicshop]

Should be all fixed now.

[mycomicshop]

Last week we took the necessary steps to close off the Heartbleed vulnerability. There's no evidence that our systems were ever attacked or affected in any way--it was just the standard stuff we needed to do to remove the vulnerability.

 

Related to all that, we requested a new certificate--the document that lets your browser make a secure https connection to our servers. Our hosting service put the new certificate in the right place for some of our virtual hosts, but not all of them. Whatever they did, it worked correctly when they tested their work, but wasn't actually fully correct. Whenever our old cert was removed, it caused the login problem you saw. Once they put the new cert in the right place, it fixed everything.

[Cyclops]

Last week we took the necessary steps to close off the Heartbleed vulnerability. There's no evidence that our systems were ever attacked or affected in any way--it was just the standard stuff we needed to do to remove the vulnerability.

 

Related to all that, we requested a new certificate--the document that lets your browser make a secure https connection to our servers. Our hosting service put the new certificate in the right place for some of our virtual hosts, but not all of them. Whatever they did, it worked correctly when they tested their work, but wasn't actually fully correct. Whenever our old cert was removed, it caused the login problem you saw. Once they put the new cert in the right place, it fixed everything.

 

(thumbs u Great to hear it's all A OK.

[Mike's Rack]

I had a book end pretty low tonight and they buyer already paid