Status
Not open for further replies.

theboynorris

New Member
Hi Guys

Have Magento installed here http://www.nirvanabeautyspa.com . We use Paypal Pro to accept payments, and onestepcheckout to simplify the checkout process.

The site is constantly getting proxy errors displayed on screen.

1) When we log into the admin, we are often faced with this error on screen, refreshing the page makes it disappear.

http://img820.imageshack.us/img820/1748/adminerror.jpg

2) When a customer tries to make payment. They are confronted with this error while the order is being processed.

http://img51.imageshack.us/img51/7676/customererror.jpg

This is the one that effects us the most, as when this error appears on screen, customers click back and re place the order. Thus, resulting in them being charged twice.

I don't think it's a magento problem, as it's all fairly standard, the core files were not edited.

The host doesn't think it's his problem, he's pointing the finger at paypal.

Paypal are saying no way, nothing to do with us.

As are onestepcheckout (this is a magento extension used to bring the checkout the process from ~5 pages to just 1)

Initially, it was just a problem on checkout, hence why paypal and onestepcheckout were involved, but the problem is happening more and more in the admin section. These errors are never seen while browsing the site / store.

I have a good knowledge of design, html, css, php, MySQL, and magento, but know very little about appache / mod_rewrite and all these other things I've been reading about on the net whilst researching the error.

I do not have full access to the server, only FTP and phpMyAdmin.

If anyone could shed any light on this error it would be fantastic.

Thanks in advance for any help.

Regards,

Brian
 

mneylon

Administrator
Staff member
The proxy error is very odd

That suggests that the access is going via another server, which sounds strange to me.
 

theboynorris

New Member
Cheers for the reply Blacknight

I'm completely lost by it, but as I said my knowledge doesn't really extend that far!

The errors occuring in the admin section I could live with, however it's proving a disaster for the business owner (who runs the site day to day), as he is getting a lot of duplicate orders. Looking at the last 10 customers that placed orders, 6 received the error, clicked back, placed order again and got charged twice.

Are you familiar with Paypal Pro? I know it isn't (or certainly wasn't up to recently) available in the south. Credit card details are entered on a secure page on our site (SSL) and they are then passed to Paypal. Paypal then pass back a "status", "all good" or "sorry they have no money", or whatever, and then the customer should receive on screen confirmation.

It's this passing back and forth of information that seems to be the problem. But then again, as I said, it has been cropping up more and more in the admin.

Any suggestions would be greatly appreciated. Would you suggest changing host (it's hosted by a web guy he used on previous projects, not with any of the big hosts, but I don't know all the details, I was just given usernames and passwords and told to put it there)

Thanks a lot for your time Blacknight

Brian
 

mneylon

Administrator
Staff member
Brian
I'm not familiar with Paypal Pro, so I can't comment on it.

Which part of the admin section is throwing the error? ie. is it only related to the Paypal stuff or is it some other part of it?

Michele
 

theboynorris

New Member
Hey Michele

The paypal pro module is built into Magento as standard. It's the same as all the others, except the customer never leaves your site. The data is collected on your SSL protected checkout page, and is then passed to payal's servers, and the customer is redirected to a confirmation page, again, on your site.

Anytime I've seen the error in the admin section is either when logging in (after clicking submit to my username + password). When I refresh the "error page", I get the magento admin main page. So I send my username and password. Get Error. Refresh Page, and I'm logged in.

Or when looking through sales / invoices. It's certainly not limited to paypal only operations.

Thank you very much for taking the time to look at this Michele.

Brian
 

mneylon

Administrator
Staff member
Brian

It's the type of error that is confusing me. If it was some sort of PHP error I'd understand, but with both of them referring to a proxy I am at a loss.
I'd wonder if there was some kind of odd multi-server setup in play .. the only thing I could suggest is to set it all up somewhere else (with a different domain or whatever - think of it as a "staging" area) and see if you get the same error.

I know several other members of the forum use Magento, so maybe they'll be able to assist you

Michele
 

php.allstar

New Member
Hi,

Lets get to the bottom of this...


  1. How long have you been using magento for?
  2. Has this problem existed since day one?
  3. Did you perform the magento installation on the live server or did you install it on a local machine then upload the files?
  4. do you have mod_proxy enabled in httpd.conf
  5. do you have any virtual host entries in your httpd.conf file? if so please list them. specifically if the have any "proxypass" declarations in them
If proxypass exists in your virtual hosts, you need to ensure mod_proxy is enabled and you have these lines in your httpd.conf file:

Code:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
 

mneylon

Administrator
Staff member
Hi,

Lets get to the bottom of this...



  1. How long have you been using magento for?
  2. Has this problem existed since day one?
  3. Did you perform the magento installation on the live server or did you install it on a local machine then upload the files?
  4. do you have mod_proxy enabled in httpd.conf
  5. do you have any virtual host entries in your httpd.conf file? if so please list them. specifically if the have any "proxypass" declarations in them

If proxypass exists in your virtual hosts, you need to ensure mod_proxy is enabled and you have these lines in your httpd.conf file:

Code:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
I think the OP only has FTP access unfortunately :(
 

theboynorris

New Member
Long answer...

The site has been in development since February last year. I came on board in November. The site was being hosted on a test server.

The site went live early December. It was moved from the test server to where it is now. I did a fresh install. A database dumb. And copied the theme folder contents from the app and skin directories.

This was not a problem on the test server. It also wasn't a problem from day one on the current hosting, but started happening about two weeks in. Since then it's gone from affecting the odd order to much much more than that. It's getting worse (or, at least it has)

4 + 5.) I have no idea, and do not have access to (/understand too good) these files.

Thanks for taking the time to reply. As I said to Michele above, I'm going to try and copy it to my own hosting and see if the problem persists.
 

php.allstar

New Member
@blacknight - ooops, I guess I should have read the first post!

@theboynorris -

Can you ask the host about my points 4 and 5 and if 5 are the lines...

Code:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1

...present?

This is more than likely an Apache configuration error - I'd like to see some packets from the network card of the server but with no shell access thats not (legally:cool:) possible...

The next time you see the error, take a note of the date and time, ask the host to provide you with the apache error.log for your site (using grep for your site on the date and time in question), it might shed some light on the situation.

I hate shared hosting, being tied down like that....VPS all the way...
 

theboynorris

New Member
@php.allstar

Hey

I contacted the current host. I sent him the date and times of the last failed transactions, and asked him to send me on the apache log. I also asked him about httpd.conf and if the lines were present.

I'm not sure how much he'll play ball, but we'll have to wait and see. I'll hopefully have some response back tomorrow.

Thanks again, to both of ye

Brian
 

theboynorris

New Member
Just heard back from him.

The site is actually hosted on a rackspace server. He has logged a support ticket with them, and has sent them on all the information I have sent him (basically this thread and more).


He's going to get back to me as soon as he hears more.

Thanks lads,

Brian
 

theboynorris

New Member
Hey lads,

Found a very interesting article here

The highlights are below

"The second change is only needed if you are using ssl pages on your site. Rackspace handles requests through a gateway server that then forwards the request to the web server running your app. The key however, is that the request is only a secure request from the user to the gateway. The request from the Rackspace gateway to the Rackspace Cloud server running Magento is send unsecured. This is not the behavior that Magento expects. The result will be an infinite loop of redirects when you try to visit any https pages on your site. A minor change to the code will fix this problem.
Rackspace includes a value “HTTP_CLUSTER_HTTPS” with the request when the request is secure. Magento normally looks for the standard “HTTPS” value. We need only make a few changes to the file \app\code\core\Mage\Core\Model\Config.php to fix this issue."


Sounds like it could be my solution. The admin section of the site is also SSL protected, so it explains the error in there too.

Will try it later, and let ye know how it goes.

Thanks again

Brian
 

php.allstar

New Member
There you go...looks like you've found your solution...let us know if it works so we'll know what to do if this happens to any of us!
 
Status
Not open for further replies.
Top