X-Payments transfer to other server with upgraded store
 

I have searched all over, but I haven't found any related info concerning transferring an x-payments installation to a different server, with an upgraded x-cart store.

I am going to upgrade a 4.4.5 store to 4.6.4 and it already uses X-Payments. The upgraded store will be located in a new server. The current x-payments is hosted in the xcart root directory. I have the following questions:

• Will I need to re-install and re-configure x-payments in the new server, or I just copy the files and database and just change any related settings, concerning the new server?
• Does the fact that x-payments will be deployed in the 4.6.4 upgraded store make any difference in the required steps?
• In X-Payments Connector admin page, there is a 'API 1.1 version is supported' line. Does this mean that the installed x-payments version is 1.1 and if not, how do I check the version of x-payments?
• Quote:

  Those who installed and started using X-Payments v1.0 can just continue doing so for any time ahead as it is acceptable for existing deployments. New deployments of X-Payments v1.0 are not allowed after October 28, 2013 due to the PCI Council regulations for PA-DSS certified applications, and we have already stopped selling this version.

  So, I guess it is not required to upgrade the current x-payments, if I don't need to use the new x-payments features related with saving customers' cc data, or for recurring billing. Is this correct?
  On the other hand, I read the following excerpt in this thread:
  
  Quote:

  So for everyone upgrading to 4.6.4 and using X-Payments - you are forced to upgrade X-Payments to its latest version 2.1.1 otherwise the new Connector will just not work properly.

  Does this hold only if you want to use the new features referred above? (saving customers' cc data, or for recurring billing)

I appreciate any tips.

Re: X-Payments transfer to other server with upgraded store
 

I would upgrade X-payments, it's easy as long as the server is setup properly.

You should have no trouble copying it and just changing the settings. No need to re-install.

Re: X-Payments transfer to other server with upgraded store
 

I believe that X-Payments can be on the same server, but in it's own Virtual Private Server area with it's own SSL.

Not sure if this has anything to do with your version, but I recently upgraded my X-Payments and found the current version in: public_facing root_folder_of_your_xpayments/config/config.ini.php It is very near the bottom of the file.

Re: X-Payments transfer to other server with upgraded store
 

No version referred in the config.ini.php - I found a version reference in the README file of the /xpayments directory. In the x-payments upgrade instructions:

Re: X-Payments transfer to other server with upgraded store
 

And this is wrong as X-Payments must be installed separately in its own hosting account/VPS/server in order to be PCI compliant.
See http://help.x-cart.com/index.php?title=X-Cart_Payments:PCI_DSS_implementation_guide

We do not recommend to install X-Payments in the same hosting space/account where you run your X-Cart shop or other software as X-Payments can be compromised via them.



You may need to adjust X-Payments config.ini.php file and shop settings in X-Payments dashboard if the new server has other IP address/domain name. Also, you may need to re-deploy configuration bundle in connected X-Cart stores due to the same reason.





X-Cart & X-Payments connection routine changed a lot in 4.6.4. Unfortunately, we haven't updated our user manual article about that yet. I am preparing a video that explains the new connection routine.




Nope, that's X-Payments API version - see http://help.x-cart.com/index.php?title=X-Payments:API
Right now there are API versions 1.1, 1.2, 1.3 which are implemented in different X-Payments versions.
The latest version of X-Payments v1.x is 1.0.6, the latest (at the moment) version of X-Payments 2.x is 2.1.1


New X-Cart v4.6.4 connector for X-Payments defines API version automatically.



If it is not a new deployment of X-Payments for a new web-site/business you can keep using your v1.x version.




Your new X-Cart 4.6.4 will work with your old X-Payments v1.x (i.e. it will process payments for orders of your shoppers) but it will not support new features of X-Payments 2.x. Also some of the usability improvements we added into new versions of X-cart connectors and X-Payments may not work either as they relay on using certain API calls we added into X-Payments v2.1.1.

Re: X-Payments transfer to other server with upgraded store
 

Would it be feasible to run x-payments upgrade in my local WAMP server (Windows 7 platform), using something like CopSSH (OpenSSH for Windows) and eventually upload it's code and database to remote server? I guess, during final data sync, there would be both x-cart store database and x-payments database sync, repeating both upgrades, after closing live store.
That would be if ssh weren't available in remote server.

As an alternative, could x-payments upgrade be run through php script?

Re: X-Payments transfer to other server with upgraded store
 

> As an alternative, could x-payments upgrade be run through php script?

Actually this is what you need to do. Every owner of X-Payments 2.x downloadable license gets access to upgrade script that makes X-Payments upgrade process a lot easier. If you have X-Payments 2.x downloadable license - just check your File Area at https://secure.x-cart.com

Btw, users of hosted X-Payments accounts do not need to worry about doing upgrade themselves. They can just send us a ticket requesting to do such upgrade free of charge.

Re: X-Payments transfer to other server with upgraded store
 

Ok, I have moved the x-payments code and database to it's separate hosting account, in the new server, with it's own SSL and trying to connect it with the upgraded x-cart store.

In the IP addresses for X-Payments callbacks (optional) of the 'X-Payments Connector' page I have already set the IP address of the new server. Also, I have updated the 'config.ini.php' file with the new database name, database user and database password (the database is the same as the one in the old server).

There are 3 issues:
1) I cannot login in the migrated x-payments back-end (https://<new x-payments hosting domain>/xpayments/admin.php), getting the usual page: The log error is:
2) In the X-Payments Connector page of the upgraded store I get the message:


3) In the 'Payment methods' tab of the migrated X-Payments Connector page, in the text: , the X-Payments backoffice link points to the x-payments old domain, instead of pointing to the new domain.

I guess, all these 3 issues are caused by the same culprit.

Have I missed some setting (for example, would I need to enter in the payment gateway account settings that is linked with x-payments and change the server path there?).
Do I need to do anything additional? I haven't upgraded x-payments, it is the original version (1.0.4) and trying to make it work with the upgraded store in the new server (as I have described in my previous posts).

Appreciate any help.

Re: X-Payments transfer to other server with upgraded store
 

Re: X-Payments transfer to other server with upgraded store
 

I can imagine that, but is there any X-Payments migration documentation that refers to settings that need to be changed, in case the same X-Payments version is transferred to a different server? The x-cart store also is upgraded.

Re: X-Payments transfer to other server with upgraded store
 

I resolved it.
I had forgotten to add the specific user to the x-payments database.

Re: X-Payments transfer to other server with upgraded store
 

Now I am getting the following message in X-Payments Connector configuration page:


X-Cart store logs:

Nevertheless, the upgraded 4.6.4 x-cart store does communicate with the migrated x-payments to the new server, since payment methods from x-payments can be re-imported.
I have to say, the only place where x-payments server IP address is defined in x-cart store admin is in the "Connection settings" tab of the X-Payments Connector configuration page, in the "IP addresses for X-Payments callbacks (optional)" setting. I cannot reach the store connection settings page, where the "X-Payment URL" setting can be set, among others. (using the 1.0.4 x-payments)

Any tips on this?

Re: X-Payments transfer to other server with upgraded store
 

I have seen this recently. I believe it should clear up once you set the x-cart store to use HTTPS on checkout and payment pages and have an SSL Certificate installed.

Re: X-Payments transfer to other server with upgraded store
 

Yes, it seems it is an SSL-missing issue, I am also getting the following error message, in 'Security' page, under 'HTTPS options' section.

Actually, I have setup the upgraded store on the new server with an IP address, with a copy of x-payments in a separate hosting account, with it's own SSL, while the old-version current store runs live in the old server.

In order to check x-payments connectivity in the upgraded store, before closing the current live old-version store, an SSL must also exist in the upgraded store environment, but this SSL currently is used for the live site (the old version).

After the current domain points to the new server, the SSL also will be transferred to this server, so I guess, only then, I will be able to check x-payments in the upgraded store.

And before this, I will close the old store and run a final database synchronization in the new server (for any recently-inserted customers, orders, etc) and also move over the final x-payments database to the x-payments new hosting account and eventually point the domain to the new server, transferring also the SSL. So, while the old store is closed and before opening the upgraded store, only then, I can test x-payments.

Is there any alternative procedure so I can test x-payments before closing the old live store and without installing an additional SSL in the upgraded store environment?

Re: X-Payments transfer to other server with upgraded store
 

What I did eventually is to change the HTTPS protocol from libCurl to OpenSSL. Also I applied the patch for POODLE vulnerability in SSLv3 (see this thread) and both the HTTPS/SSL check warning and the
error message stopped appearing.
I presume that the X-Payments Connector works ok, although I haven't found any 'Test Module' button to run a connectivity test.

Re: X-Payments transfer to other server with upgraded store
 

> although I haven't found any 'Test Module' button to run a connectivity test.

It has been removed in 4.6.4 and new connection routine is now in place - see http://help.x-cart.com/index.php?title=X-Cart:X-Payments_Connector#X-Payments_2.1.x_and_new_X-Cart_connector_modules

Re: X-Payments transfer to other server with upgraded store
 

Alex, I have the old 1.0.4 X-Payments version (as stated in previous posts in this thread).

Re: X-Payments transfer to other server with upgraded store
 

You should to upgrade to at least 1.0.6 and the new connectors work with X-Payments 1.x, too.

Re: X-Payments transfer to other server with upgraded store
 

• Quote:

  You should to upgrade to at least 1.0.6 and the new connectors work with X-Payments 1.x, too.

  Is the upgrade to 1.0.6 required for correct functionality of the X-Payments Connector in the 4.6.4 upgraded store, or can it work with 1.0.4 version?

• Does this upgrade need a payed licence? I don't seem to find 1.0.6 version in my File Area.

• Some recent orders have a 'Failed' status, with the following logs:
  
  Payment gateway log: ("Order Details" page):
  Quote:

  --- Advanced info --- Reason: Internal error (Response is not valid.<br />Check logs.) CVV info: not set /

  
  X-Cart store log:
  Quote:

  [03-Nov-2014 13:28:57] (shop: 03-Nov-2014 14:28:57) PAYMENTS message: Payment processing failure. Login: username IP: 104.10.42.129 ---- Payment method: Credit Card (Pay on next page) (X-Payments: Authorize.Net AIM) bill_output = Array ( [cvvmes] => not set / [code] => 2 [billmes] => Internal error (Response is not valid.<br />Check logs.) ) original_bill_output = Array ( [cvvmes] => not set / [code] => 2 [billmes] => Internal error (Response is not valid.<br />Check logs.) ) Request URI: /shop/payment/payment_cc.php Backtrace: /home/domain/public_html/shop/payment/payment_ccmid.php:460 /home/domain/public_html/shop/payment/payment_ccend.php:48 /home/domain/public_html/shop/payment/payment_cc.php:359

• Do the above mean that a CVV code was not input by the customer during checkout, or is it an internal x-payments error which needs fix?

• in case it needs a fix, would the upgrade to 1.0.6 most probably fix it?

• Also, when I attempted to re-deploy the configuration bundle, I got a popup warning:

. The database has been transferred from the old server to the new server (as described in the previous posts), with the same online store details. The store domain is the same, just different server and store upgrade. Should I re-add the store to X-Payments?

Re: X-Payments transfer to other server with upgraded store
 

> Is the upgrade to 1.0.6 required for correct functionality of the X-Payments
> Connector in the 4.6.4 upgraded store, or can it work with 1.0.4 version?

It is recommended. We did not test the new connectors with X-Payments versions earlier than 1.0.6. Besides 1.0.6 has many bug-fixes vs 1.0.4


> Does this upgrade need a payed licence?

Every owner of X-Payments 1.x downloadable license has free access to all versions within 1.x branch. 1.0.6 is the last version we developed in 1.x branch.


> I don't seem to find 1.0.6 version in my File Area.

I advise you to contact our CR reps via your HelpDesk account regarding this.

Re: X-Payments transfer to other server with upgraded store
 

Finally I upgraded 1.0.4 to 2.1.1, using via SSH and when I attempt to login in the x-payments admin I get the following error: :(

In the putty console, after the upgrade, it displayed:

Any tips?

Re: X-Payments transfer to other server with upgraded store
 

I removed the upgraded version, re-installed the 1.0.4 version and I re-upgraded to 2.1.1 and I could enter the back-end, but now, when I click on the enabled online store to check it's details, I get:

When I tried to re-login in the back-end, I got again , as described in my previous post.

Re: X-Payments transfer to other server with upgraded store
 

You need to generate new codes.

Default codes contained in <lib/XPay/Model/Codebook.php> must be changed after the installation is done. Use maintenance script regen-codebook.php to generate a new codebook.

http://help.x-cart.com/index.php?title=X-Payments:Regen-codebook.php

Re: X-Payments transfer to other server with upgraded store
 

In my previous post, I wrote . I need to correct this phrase, I didn't actually do any installation, just transferred the 1.0.4 code and database back to the server, so it had it's codebook already.

Besides, I attempted to regenerate the codebook, but I got some fatal error messages during the regen, so I cannot regenerate codebook either, nor I can login in the backend.

Internal Error during new password setting
 

Just installed latest X-Payments version from scratch. All went ok during installation and got into the backend, alright.
After regenerating the codebook, and the procedure went ok, I got the last account activation email with the new pin codes. I attempt to set the new password, but I get the following page:
The logs say:

errors.0001.log:

access.0001.log


I regenerated the codebook a 2nd time and again got the same error.

I have followed the installation instructions to the letter.
Now, what could the logic be behind this 'CODEBOOK_KEY_NOT_FOUND' message, especially since I just regenerated the codebook. Why should a key be missing, since everything is just newly regenerated? Does it make a sense?

After having read almost the whole X-Payments subforum for just upgrading or installing X-Payments and getting stuck in the initial stage of X-Payments management (installation), I start to believe that it is either a VERY BUGGY software, or the documentation lacks a lot. I am impressed 8O

Appreciate any help.

Re: Internal Error during new password setting
 

I am really sorry to see you can't get X-Payments installed on your hosting. I am not sure what's wrong as I do not know where your X-Payments is installed and do not know details of server environment there. Feel free to PM me everything, but I advise you to post a technical support ticket using your HelpDesk account as it looks like a technical guy from our team need to go into your server and see what's wrong there.

Crypt_cell_is_not_detected (1311)
 

Have just fresh installed X-Payments 2.1.1 on a 4.6.4 store, having connected it with Authorize.NET AIM payment method.

When I submit test orders I get to the X-Payments cc form page, but I get Failed transactions, with
message in the Payment gateway log section of the order details and no log error in the X-Cart store, concerning X-Payments Connector errors.

In the X-Payments backend, these orders are listed under "Pending" status.

No reports for these transactions are created in the Authorize.NET backoffice side.

In the X-Payments logs though, I see the following errors:

Any idea what this cryptic message means, or how to fix this?

Re: X-Payments transfer to other server with upgraded store
 

All threads were merged as they are literally about the same issue - something wrong with your new X-Payments install.

Unfortunately, nobody can help you with that as someone needs to go into your server and see what's wrong there. Nobody else has all those issues and I am pretty sure this is either server-specific or it was a wrong upgrade or install.

Anyways, a tech need to go into your servers and check there.

Re: X-Payments transfer to other server with upgraded store
 

I have the same error
There were no changes to configuration at all, last payment we received was 2 days ago. Lost a couple of orders before we realized something wrong with xpayments.
I'm going to upgrade from 2.1.1 to 2.1.3 to see if it change anything.

Re: X-Payments transfer to other server with upgraded store
 

It could be your X-Cart server still supporting SSLv3 and your X-Payments server not supporting it.

Check what SSL you have enabled on your X-Cart and X-Payments servers first. And your X-Cart and/or X-Payments could be not patched to remove explisit call of SSLv3 while your server environment does not support SSLv3 already.

See http://forum.x-cart.com/showthread.php?t=70268

Re: X-Payments transfer to other server with upgraded store
 

upgraded successfully, but didn't help
Will check SSLv3

Re: X-Payments transfer to other server with upgraded store
 

Everything is updated, SSLv3 is disabled a long time ago, but still
I have no idea where to dig

Re: X-Payments transfer to other server with upgraded store
 

> I have no idea where to dig

I suggest to contact our techs using your HelpDesk account, but usually in such situations they just find something was not patched or SSLv3 still being used by the software.