License Problems

[Jim McCormick]

I have a similar problem.

I have several miva merchants installed (4.34), and I recently installed a version 5 (running empresa 5.04).

It installed fine and registered fine.... months ago.

I am now out of testing mode and trying to change my domain in domain settings. I'm getting the same error about establishing a secured connection to miva's licensing server.

I don't know how it worked when first installed, but all my other miva stores (which of course, have a secured cert), work fine to change the domain settings and update thru miva's registration server.

Just with this new store, which doesn't have any certs yet, won't work to update with the licensing server.

If you go to https://licensing2.smallbusiness.miv...way/gateway.mv
in a browser, it says their cert is not valid. I dunno (since my other ones work), but could this be an issue in merchant 5? Does my server, or merchant not like the fact that miva's cert is not valid?

Just throwing out some ideas.

If you are getting this error:
Error establishing SSL connection: certificate verify failed

OpenSSL is either not conifgured correctly or your firewall is blocking outbound on 443. First check the OpenSSl configuration as that is the cause 9 times out of 10. If you have our diag5.mvc tool, the license check will check all the secure calls as well.

[rich1000]

If you are getting this error:
Error establishing SSL connection: certificate verify failed

OpenSSL is either not conifgured correctly or your firewall is blocking outbound on 443. First check the OpenSSl configuration as that is the cause 9 times out of 10. If you have our diag5.mvc tool, the license check will check all the secure calls as well.

Yeah, I figured it out. I added the variables to my httpd.conf file for all the SSL stuff. I guess I was thrown off by the fact that I thought I needed to be in the miva admin with a https connection. When in fact, I just needed miva to have the SSL configured to do the send out.

Thanks. I guess i just needed to keep trying what you guys were talking about specifically.

[d_host]

Jim,

Once again, I think you need to verify your SSL certificates and make sure they are installed on the correct hosts. https://licensing2.smallbusiness.miva.com has SSL installed on it that belongs to https://licensing.smallbusiness.miva.com (without the "2" in "licensing"). This has happened once or 10 times before and it's happening this very minute when I'm looking at it from here. For the record, it's Friday Aug.4, 7:26pm PST. This would explain the problem trying to make a proper SSL connection as the SSL doesn't match the host name.

[Quiche Jackson]

Testing the MIVA Licnese Manager

The suggested method to test the MIVA License Manager is to use the tool below:

MIVA Diagnostic Application 5

You can download this tool from the support center download area:
http://support.smallbusiness.miva.co...itemid=1&nav=0

MIVA License Manager Call
This test simulates the MIVA Merchant calls to the MIVA License Manager.
Use this test to determine if your site is able to communicate to the MIVA License Manager, best for troubleshooting errors during setup or upgrade regarding your MIVA software license numbers.

It is important to understand that accessing the License Manager URLs directly in a browser is not the same as running the test in the diag5.mvc tool or the processes built in to the MIVA Software.

Currently the only way to determine if MIVA Software is having trouble with communicating with the MIVA License Manager is to use the 'MIVA Diagnostic Application 5' License Manager Call test.

If all the URLs in the License Manager Call test show up in green then you know the MIVA Software can also communicate with the License Manager correctly. If any of the URLs show up in red then you know that your MIVA software may not communicate with the MIVA License Manager correctly.

NOTE: * If a single URL shows up in red this does not necessarily mean that your MIVA Software will not communicate with the MIVA License Manager correctly, this is because the software is designed to use the other URLs as a form of licensing redundancy.

Below is a screenshot of a successful MIVA License Manager Call test:

[mgobeil]

Error establishing SSL

We have the same problems twice now !

First time we had to re linitalize Merchant 5

Tech support is verry poor unless you pay but why pay for somthing is buggy ?

they keep telling me it is a ssl problem on our end but what does ssl at our end have to do with acessing there url?

I am sorry I baught this softwear now !

Unable to open URL 'https://licensing.smallbusiness.miva.com/gateway/gateway.mv': Error establishing SSL connection: certificate verify failed
Unable to open URL 'https://licensing2.smallbusiness.miva.com/gateway/gateway.mv': Error establishing SSL connection: certificate verify failed
Unable to open URL 'https://licensemgr.miva.com/gateway/gateway.mv': Error establishing SSL connection: certificate verify failed

[mgobeil]

This is what i get when I try to access there licence url

Test Page
This page is used to test the proper operation of the Apache Web server after it has been installed. If you can read this page, it means that the Apache Web server installed at this site is working properly.
--------------------------------------------------------------------------------

If you are the administrator of this website:
You may now add content to this directory, and replace this page. Note that until you do so, people visiting your website will see this page, and not your content.

If you have upgraded from Red Hat Linux 6.2 and earlier, then you are seeing this page because the default DocumentRoot set in /etc/httpd/conf/httpd.conf has changed. Any subdirectories which existed under /home/httpd should now be moved to /var/www. Alternatively, the contents of /var/www can be moved to /home/httpd, and the configuration file can be updated accordingly.


--------------------------------------------------------------------------------

If you are a member of the general public:
The fact that you are seeing this page indicates that the website you just visited is either experiencing problems, or is undergoing routine maintenance.

If you would like to let the administrators of this website know that you've seen this page instead of the page you expected, you should send them e-mail. In general, mail sent to the name "webmaster" and directed to the website's domain should reach the appropriate person.

For example, if you experienced problems while visiting www.example.com, you should send e-mail to "[email protected]".


--------------------------------------------------------------------------------

The Apache documentation has been included with this distribution.

For documentation and information on Red Hat Linux, please visit the Red Hat, Inc. website. The manual for Red Hat Linux is available here.

You are free to use the image below on an Apache-powered Web server. Thanks for using Apache!



You are free to use the image below on a Red Hat Linux-powered Web server. Thanks for using Red Hat Linux!

[Vic - WolfPaw Computers]

Accessing it how?

There is no reason to access the license server unless you are passing data to be validated against the license key.

[mgobeil]

ok so

This site was up and running for 2-3 months and now we do a password change and it breaks at the end of the day this is what I am trying to say !

[mgobeil]

Well I wipe the egg of my face and apolgize
Turns out it was a setting in -- Ubuntu
SetEnv MVCONFIG_DIR_CA

[miv_n3wb]

To clarify the solution, we had to make an additional entry in Apache's httpd.conf:
SetEnv MVCONFIG_DIR_CA /etc/ssl/certs

This would also have worked:
SetEnv MVCONFIG_DIR_CA /home/miva/certs

I am very frustrated that the Miva tech support could not have provided us with the answer when the solution itself was so simple. This had nothing to do with the OS itself - it's a Miva configuration variable. I had to use the "strings" utility on miva's shared libraries in order to find this environment variable. This was after about 5 or 6 hours of troubleshooting the system.

-BF

[Jim McCormick]

Re: License Problems

To clarify the solution, we had to make an additional entry in Apache's httpd.conf:
SetEnv MVCONFIG_DIR_CA /etc/ssl/certs

This would also have worked:
SetEnv MVCONFIG_DIR_CA /home/miva/certs

I am very frustrated that the Miva tech support could not have provided us with the answer when the solution itself was so simple. This had nothing to do with the OS itself - it's a Miva configuration variable. I had to use the "strings" utility on miva's shared libraries in order to find this environment variable. This was after about 5 or 6 hours of troubleshooting the system.

-BF

This was mentioned in a previous post in this thread:


When you have an issue like this, it's 1 of a few things:
1. OpenSSL is not configured correctly or not even configured
2. certs are not configured correctly
3. firewall blocking outbound on port 443