globalsign ssl blank page in step 2

[adtastichosting]

Ok I just installed globalsignssl and activated my partner registration with globalsign including putting some money in the account over there.

 

I configured an ssl cert in my cart following the instructions in the wiki. I ran some tests and everything went thru fine. So I unticked testing mode and bought myself a real cert with a real csr. When I got the ssl certificate configuration email I followed the link and submitted the csr and pertinent info. (BTW even though I have the latest version of WHMCS I found out the configuration email used the old codes which had to be fixed)

 

Anyways, when I enter to continue from step one (entering the CSR and pertinent info) it goes to step two ie: configuressl.php?cert=xxxxx&step=2

 

This is a blank page. Oops, something not working here. Is it maybe a corrupt configuressl.php or did I need to set some permissions on this file or the globalsignssl directory in my install that wasn't mentioned in the setup docs or has anyone else experienced this or???

 

Well, I turned on the configuration for to display errors and here we go:

 

Fatal error: Class 'SoapClient' not found in /xxxxxx/xxxxxxx/xxxxxx/servers/globalsignssl/globalsignssl.php on line 135

 

So I assume I have to rebuild php on this server to include SOAP. Darn, if it isn't one thing it is something else.

Edited May 22, 2010 by adtastichosting

[adtastichosting]

Ok, I successfully answered my first question/issue by recompiling php to include soap. No more blank page. Now I get a "server misconfiguration error" when I try to submit the csr. I looked at the server error log and this is what I see:

 

Premature end of script headers: configuresssl.php, referer: (site address here).

 

The script is encrypted so I can't look at it to even see what is going on there. Of course the above error means the script (configuressl.php) is stopping for some reason but why?? Since i don't even know what step 2 does, hard to troubleshoot.

 

Also too, in the interest of trying to provide as much detail as possible, might mention, we have configserver firewall and mod security on this server. As well, php's open_basedir protection is exempted from this particular site. suphp is the php 5 handler and apachesuEXEC is on. Surely it is some sort of configuration on the server we should address/modify?

 

Any one have ideas about this?

[adtastichosting]

Ok, I successfully answered my first question/issue by recompiling php to include soap. No more blank page. Now I get a "server misconfiguration error" when I try to submit the csr. I looked at the server error log and this is what I see:

 

Premature end of script headers: configuresssl.php, referer: (site address here).

 

The script is encrypted so I can't look at it to even see what is going on there. Of course the above error means the script (configuressl.php) is stopping for some reason but why?? Since i don't even know what step 2 does, hard to troubleshoot.

 

Also too, in the interest of trying to provide as much detail as possible, might mention, we have configserver firewall and mod security on this server. As well, php's open_basedir protection is exempted from this particular site. suphp is the php 5 handler and apachesuEXEC is on. Surely it is some sort of configuration on the server we should address/modify?

 

Any one have ideas about this?

 

Any one have any troubleshooting ideas on why the globalsign ssl module isn't working on my server per the above issue? my understanding that the "premature ending of script headers" is very common in that the script simply stopped for some reason before outputting anything to the web server. Since the actual script is all encrypted I wouldn't really know what or where to add a line to maybe get it to send any errors to the browser so I can troubleshoot it as in the case of for example it using perl.

 

Before submitting a ticket on it figured I'd fish around on here and see if anyone that might be familiar with it can think of something for me to try.

[papapan]

Hi,

Did you find any solution? I have exactly the same problem.

 

Any one have any troubleshooting ideas on why the globalsign ssl module isn't working on my server per the above issue? my understanding that the "premature ending of script headers" is very common in that the script simply stopped for some reason before outputting anything to the web server. Since the actual script is all encrypted I wouldn't really know what or where to add a line to maybe get it to send any errors to the browser so I can troubleshoot it as in the case of for example it using perl.

 

Before submitting a ticket on it figured I'd fish around on here and see if anyone that might be familiar with it can think of something for me to try.

[adtastichosting]

Hi,

Did you find any solution? I have exactly the same problem.

 

Nope- as you can see here this thread hasn't received any answer at all. I haven't found the answer on my own so at present have given up on it.

[netearth]

Hi there,

 

THis wont help much but to show that it does work, we have configured a few of these working with our resellers, so we know Matt's code is working.

 

Suggest, backup site, and reload the gs module as well as the configuressl files too.

 

Chris

[adtastichosting]

Hi there,

 

THis wont help much but to show that it does work, we have configured a few of these working with our resellers, so we know Matt's code is working.

 

Suggest, backup site, and reload the gs module as well as the configuressl files too.

 

Chris

 

I'm certain it works, perhaps for most even. It works here up until you get the email with the link to go in and configure the ssl. Then when you click submit we simply get the

" Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request." Obviously this is when it is supposed to be transmitting to globalsign. I've checked the server error logs and as mentioned before it only shows "premature ending of script headers" which is a rather difficult one to troubleshoot since the actual script both configuressl.php and globalsignssl.php are encrypted files. I tried the suggestion of reloading the files but that doesn't seem to be the issue. It might help if we know what it is doing at that moment maybe there is something in our server security configuration or something in perl or php or soap that we need to (re)configure or who knows..

[rdavis]

This is a copy of our support ticket email to WHMCS so others can find help too. We will post it here after we find a solution with WHMCS's help!

 

And BTW, yesterday we had no delay or signup issues from GlobalSign as a WHMCS affiliate. They completed our paperwork and activated our affiliate account all in one 24 hour day!

 

Yes, our rep is also Frank Romito, Channel Sales Manager.

 

Thanks for reading this!

 

 

Support Ticket:

After bringing our GlobalSign module online this morning, as a TEST, a real client purchased and used (mail in, as a payment test) then after our manual acceptance of (mail in) payment posted to their account, the GlobalSign module did not auto create as described in the online installation instructions right after our acceptance of their order! So through the clients profile ( products tab) we manually used "CREATE" and so it did.

 

It sent an email (with the link back to our site) to the client as it should. After the client filled out the necessary information from this online script and pressed the acknowledgment button the online page moved to display an online error of # - 6101 - Balance Error #

 

According to our rep of GlobalSign as a "Pay As You Go Affiliate" we need no balance in our account as the system processes in 3 ways and allows for a transaction to be completed without immediate payment from our affiliate account.

 

 

So we have no idea what went wrong, and have telephoned our rep and left a MSG with no call back yet, as of this support ticket

 

 

Client Info:

Registration Date: 06/09/2010

Product/Service: SSL Certificates - AlphaSSL Certificate

Validity Period:: 1 Year

SSL Installation Service: None

Payment Method: Mail In Payment

First Payment Amount: $XXXXX USD

Recurring Amount: $0.00 USD

Next Due Date: -

Billing Cycle: One Time

Status: Active

[adtastichosting]

Hope you find an answer to your issue. Unfortunately it isn't related to the issue of this thread which is that after you get the email to click the link and enter your csr details to be transmitted to globalsign to set up the ssl when you click submit you simply get the

" Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request."

[rdavis]

Yes, your right (not specifically related) but close!

 

We did get past your issue and did fill in all the required SSL info that was needed, CRS and all! Then at that point, submitting the information back to GlobalSign (press acknowledge) is when we received the online error of # - 6101 - Balance Error # right after.

 

Sounds to me like the same location, different outcome! Strange things a-foot Watson!

 

My 1st guess is the API looked into our affiliate account balance of funds and found a zero balance, instead of completing the transaction as one of the (3) three options of payment as outlined in GlobalSign's affiliates documentation, "The option of being billed at the end of each month."

 

So until we talk to our rep or he calls us back, I guess we wont sell any SSL certificates!

We certainly will not be funding our affiliate account with $1,500.00 as they would like.

 

So now that I have said all this, I think I'll try it again! Just to see what's going on.

 

Thanks

Edited June 10, 2010 by rdavis
additional thought and bad spelling!

[rdavis]

Yes, your right (not specifically related) but close!

 

We did get past your issue and did fill in all the required SSL info that was needed, CRS and all! Then at that point, submitting the information back to GlobalSign (press acknowledge) is when we received the online error of # - 6101 - Balance Error # right after.

 

Sounds to me like the same location, different outcome! Strange things a-foot Watson!

 

My 1st guess is the API looked into our affiliate account balance of funds and found a zero balance, instead of completing the transaction as one of the (3) three options of payment as outlined in GlobalSign's affiliates documentation, "The option of being billed at the end of each month."

 

So until we talk to our rep or he calls us back, I guess we wont sell any SSL certificates!

We certainly will not be funding our affiliate account with $1,500.00 as they would like.

 

So now that I have said all this, I think I'll try it again! Just to see what's going on.

 

Thanks

 

 

 

Update: :arrow:

 

We did contact GlobalSigns and found exactly what WHMCS support and I suspicioned "an account funding issue". The WHMCS GlobalSign module worked correctly, but the transaction did not complete until we contacted our GlobalSign representative and a modification to our WHMCS Affiliate Reseller's account was made.

 

More details about our resellers account modification by GlobalSign to follow....

 

Thanks for reading.

[spectrumhosting]

Also fails for me .. my rep stopped answering my emails and now I have a general support ticket open .. still waiting for a response after 7 days.

 

It looks promising, but the support has been disappointing.

 

I can provision certs fime through their website, just not through my WHMCS and that's why I bought credit with them.

 

Mike Boyle is my rep .. I know he's on holidays now, but he wasn't for 3 weeks I was chasing him for support.