USPS Error

[CygnusFTK]

You unzipped the file and loaded the curltester.php into your directory:
your_domain_name.com/extras/curltester.php

correct?

https://dragonherbarium.com/extras/curltester.php

[Ajeh]

Do you have any other files in the /extras directory?

[CygnusFTK]

Do you have any other files in the /extras directory?

SMART! I did. Deleted everything else and now get results.

Everything comes back as GOOD.

Connecting to USPS (port 80)...
GOOD: CURL Connection successful.

Connecting to USPS Test/Staging/Sandbox Server (port 80)...
GOOD: CURL Connection successful.

[Ajeh]

Could you go to your Modules ... Shipping ... and set it to Debug to the Logs ... then try to do a checkout shipping and then look in /logs and Zip the shipping log and add it to your next post?

[CygnusFTK]

log.zip

These look like the important lines:

[04-Sep-2015 03:02:11 UTC] PHP Warning: file_get_contents(): http:// wrapper is disabled in the server configuration by allow_url_fopen=0 in

/hermes/waloraweb086/b948/pow.dragonherbar/htdocs/includes/modules/shipping/usps.php on line 2290
[04-Sep-2015 03:02:11 UTC] PHP Warning: file_get_contents(http://www.zen-cart.com/downloads.ph...heck&id=1292): failed to open stream: no

suitable wrapper could be found in /hermes/waloraweb086/b948/pow.dragonherbar/htdocs/includes/modules/shipping/usps.php on line 2290
[04-Sep-2015 03:02:11 UTC] PHP Warning: in_array() expects parameter 2 to be array, null given in

/hermes/waloraweb086/b948/pow.dragonherbar/htdocs/includes/modules/shipping/usps.php on line 2294

[DrByte]

I am also having an issue. We had no problem with this at all until a few days ago. Now, nothing that I can do is working with USPS.

The most important part of that sentence is "we had no problem at all until a few days ago".
.. which begs the question: what happened a few days ago?

Did you change something?

Did you alter your Zen Cart site somehow?

I can tell you that Zen Cart does NOT mysteriously change itself.

So ... something happened.

And if it wasn't "you", then who?
Maybe your hosting company? Have you asked? Did they change something in their firewall? Maybe something in PHP? Maybe someone else on your same server got hacked and your hosting company silently implemented a bunch of changes to tighten things up, not realizing it's affecting others without notice.

Or ... were you hacked? Did someone make unauthorized changes to the files in your Zen Cart site? Have you checked that all your files are present and accounted for, and none have been altered without your knowledge? Ref: http://www.zen-cart.com/wiki/index.p...ing_From_Hacks

I am seriously ready to start looking into other shopping cart solutions as this has completely taken our store down.

I remind you: Zen Cart itself didn't suddenly just decide to refuse to work. Something caused it, and your job is now to find out what, and fix it, and prevent it from happening again. Changing software won't help anything if the real problem is a server security issue that needs fixing, or a hosting issue that can be fixed by the hosting company.

https://dragonherbarium.com/extras/curltester.php

The curltester.php script has revealed that it's not a general communications problem. So I suspect it's something wrong with unexpected changes made to your Zen Cart files.

I suspect your site is encountering numerous errors, some of which you can't see because they're being silently recorded in logs (so that hackers can't abuse the info that could otherwise be revealed in such error messages).
Two places to look are:
- your site's /logs/ folder ... as per http://www.zen-cart.com/content.php?124-blank-page
- your server's control panel, in the Apache Error Log area

[DrByte]

[04-Sep-2015 03:02:11 UTC] PHP Warning: file_get_contents(): http:// wrapper is disabled in the server configuration by allow_url_fopen=0 ...

That's caused by your server's PHP configuration disallowing the file_get_contents() function from accessing external URLs. The USPS module is simply checking for whether a newer version is available. That's the only time is uses the file_get_contents() function, so that warning can be ignored ... except that you'll have to manually check for new versions yourself and not rely on the convenience offered by a server which allows the automated checking (yours doesn't ... again probably because other accounts on your same server have been hacked and your hosting company figures this allow_url_fopen setting is something they don't know how to secure so they just shut it off instead).

The USPS module doesn't use file_get_contents() to check for shipping quotes. It uses CURL for that .. hence the curltester.php script which emulates the same communications connection to USPS that the Zen Cart shipping module itself does.

[CygnusFTK]

Well, I am the only one AUTHORIZED to make changes but that doesn't mean that I am the only one who does. I have made no changes other than to get rid of Authorize.net as a payment module. I am not sure how that would have affected the USPS shipping module, however.

We actually did just start noticing some other errors, as well. The scariest is the 500 Internal Server Error that just started happening in check out. That was going to be the next issue that I am going to dig my teeth into but I guess these two are probably related.

Your last link was not relevant to this discussion, I don't think. I am not getting a blank page.

I am wondering. I think that the person I took this project over from started to upgrade but never finished it. I wonder if there is a versioning disconnect between the files and the database and if that could be causing an issue. Thoughts on that?

Guh. What a mess. Inherited projects...

[DrByte]

We actually did just start noticing some other errors, as well. The scariest is the 500 Internal Server Error that just started happening in check out. That was going to be the next issue that I am going to dig my teeth into but I guess these two are probably related.

Yes, to some degree they probably are. The Apache error log will give you the explanation of the "500" error.

Your last link was not relevant to this discussion, I don't think. I am not getting a blank page.

Perhaps not a blank page, but the article is more about learning to use the files in the /logs/ folder to discover ongoing PHP errors being triggered by your site. It's not only about blank pages, but blank (or partially-blank) pages are the most common entry point to that discussion.

I am wondering. I think that the person I took this project over from started to upgrade but never finished it. I wonder if there is a versioning disconnect between the files and the database and if that could be causing an issue. Thoughts on that?

Perhaps, but in what way does that intersect with this "sudden" usps problem?

I do agree that completing an upgrade is usually beneficial. But you probably want to fix the checkout problem first so that sales can resume. Unless the problem is truly related to a started-but-never-finished upgrade done directly on the live site, then I'd focus on fixing the "sudden" problem first.

[DrByte]

I am also having an issue. We had no problem with this at all until a few days ago. Now, nothing that I can do is working with USPS.

The first person posting in this discussion posted an actual error: "Error 28: connect() timed out!"

But, you've not actually stated what the specific symptoms are for your situation.
What exactly are you observing to be happening?