Camelot-Hosting down?

yd29999:

To save you some hair in the future I follow these rules.

1. If a server is coming up or if something stops working when I haven't made any changes I go to the hosting company.

2. If I'm fiddling and something breaks I look in the mirror then I try to retrace my steps.

3. If I'm installing a mod and I think I did everything right then I got to the mod forum or search zc.

Those are good rules to go by. :bigups:

What I would also add is:

4. When replacing altered files save the ones on the hosting account by renaming them, adding the number 1 or _orig at the end (...php1 or ...php_orig).

Then if things go bad, delete the newly uploaded file and change the name back to what is was. You are instantly back where you were.

I'm not sure if numbering is a good idea , as *.php4 and *.php5 are in most systems real extensions. This may cause the files to be run unintended.

hdwrkgr:

Thank you the recommendation, I just submitted a ticket to Camelot. I want to state the issue I am have so that as soon as it is resolved I will post the solution, this is in an attempt to save someone with the same issue time in resolving the problem [because of this ongoing issue hdworkgear is essentially still broken since the server melt-down, now day 10]:

Since the server come back PayPal [PP] has not been able to communicate with my admin page, PP is able to captures the cart and customer payment information, but when the customer confirms the order an error messages occur: 10415 and 10002/API Security Incorrect. PP does capture the payment, but there is no record of the transaction recorded at the admin page. The customer is informed that an error occurred and instructed to refresh the page.

After numerous calls to PP and installing new API credentials at the payment module and tweaking my email settings, same errors continue to show, PP claims the problem is on the server side?

if PP captures the payment, then there is no question that the problem is on the server side. PP got you your money, they send back something, and now your host/ZC is having trouble processing the return string. for whatever reason....

a 10415 means a duplicate transaction. search this document for 10415:

http://www.callingmart.com/support/faq/attachments/paypal%20error%20codes.pdf

it is possible that when the customer receives the first error, they refresh the page, which resubmits the order resulting in a duplicate transaction.

a 10002 error is far more generic, and looks to be a problem with security credentials. although that is tough to tell....

good luck!

Hello Scott
I will now look into the SSL situation, I am thinking of actually updating it, as the site is still not processing credit carts. TY

I just noticed that on the 7/13, 7/14 and 7/15 the site has lots of hits, I think its a robot is trying to brute force open the site; I have had a lot of that coming from France and was able to block access. Q: if my SSL is possibly in question does that make the site vulnerable?

hdwrkgr:

I just noticed that on the 7/13, 7/14 and 7/15 the site has lots of hits, I think its a robot is trying to brute force open the site; I have had a lot of that coming from France and was able to block access. Q: if my SSL is possibly in question does that make the site vulnerable?

i have no idea what that means, to brute force open the site. robots scan websites so that they can index them, or perhaps look for open ports (if malicious).... your site is open....

your site is vulnerable if you do not follow good coding practices. or if you use weak passwords....

and what makes you think your SSL is in question? it looks fine to me. see:

https://www.ssllabs.com/ssltest/analyze.html?d=www.hdworkgear.com

i would focus on getting paypal working and not worry about all of this other stuff....

carlwhat:

i have no idea what that means, to brute force open the site. robots scan websites so that they can index them, or perhaps look for open ports (if malicious).... your site is open....

your site is vulnerable if you do not follow good coding practices. or if you use weak passwords....

and what makes you think your SSL is in question? it looks fine to me. see:

https://www.ssllabs.com/ssltest/analyze.html?d=www.hdworkgear.com

i would focus on getting paypal working and not worry about all of this other stuff....

I have truly come to appreciate this support site, you Zenners are a special group of people and this particular thread showed me a generous amount of goodwill. Through it all, I am happy to say my site is now healthy; the error was caused by an old addon that created a new DB resulting in an error that creating a negated entry, Anthony Corbett of Camelot called upon many of his friends here to help him with the troubleshooting. I plan on visiting this site more often as many of your names are now familiar to me. Best wishes!

Does anyone know why my site is saying that it's NOT secure any more, I THINK since this crash...?

I get the attached image message at top (URL) in Chrome. It was just brought to my attention by a customer.

Chrome has the "i" in a circle, rather than the lock, showing "secure"... It used to show secure, I'm pretty sure.

Thanks!

http://www.zdnet.com/article/google-tightens-noose-on-http-chrome-to-stick-not-secure-on-pages-with-search-fields/

barco57:

http://www.zdnet.com/article/google-tightens-noose-on-http-chrome-to-stick-not-secure-on-pages-with-search-fields/

What's odd is that our site is using https:, not http:, as in that article referenced...

What a PITA for me to have to go through this and figure out what's causing this.

Put a ticket in and see what Tony has to say.

yd29999:

Put a ticket in and see what Tony has to say.

Yes, I did, and he says it's because of images that are not https, but I don't know which ones yet, and am going to have to spend time looking through code, etc. Seems like I did this a few years ago for a similar problem, but only had to remove some sideboxes.

It just sends customers into a frenzy when they see "not secure", when it really is, 99.99% of the time.

I think you missed the point.... Yes, you use https on secure pages, but the browsers are now warning against HTTP. I can go to http://vtstuff.com and cruise around the entire site http until I go to the login page and then it switches to https. The browser vendors are pushing for https everywhere all of the time.

Moved the posts from @vtstuff and responses regarding failing saves to a new thread. Follow ups here please:
https://www.zen-cart.com/showthread.php?223154-Save-failing