| Reseller Help: Reseller Tools Help : Reseller Initial Test Environment (RITE) | |
| Can I delete a domain registered on the test server in error? | |
| Why am I am getting an empty Email with each of my registrations? | |
| Why can't I complete test registrations because of invalid nameservers? | |
| Why can/can't I register a name that's available/unavailable on the Internet? | |
| Why can't I connect to horizon.opensrs.net with verify_install.cgi? | |
| Why do I get "unable to open socket" authenticating with verify_install.cgi? | |
| Why do the HTML files in the templates directory have {{CGI}} tags in them? | |
| Do I need to manually process each domain from Pending if I use reg_system.cgi? | |
| What could be wrong if I am getting an "internal server error" on the scripts? | |
| What's the difference between register.cgi and reg_system.cgi? | |
| What policies have to have posted on my site in order to be an OpenSRS RSP? | |
Q:Can I delete a domain registered on the test server in error? | |
A:If you are using OpenSRS client software or the Quickstart Web interface ("Place Order Manually") in the Test environment (horizon.opensrs.net), then don't worry. Nothing on the Internet has been affected by what you've done. The dollars you spend in the test environment are not real and do not take real money out of your account - you won't be charged for them. However, domains can't be deleted from the test environment. If you're in the production ("live") environment and made a registration error, see this question in the Production environment section. | |
 | |
|
Q:Why am I am getting an empty Email with each of my registrations? | |
A:If you are getting an Email that looks like this: ...after each of your registrations, then you have turned on the option for sending confirmation Email, but didn't actually configure the message. In either the test (http://resellers-test.opensrs.net) or the production (http://resellers.opensrs.net) environment Web interface main page, select "Tech Contact Information". At the bottom of that page is a checkbox option to "Send email when domain is processed" and links to "Configure Message" and "Configure Message to Customer when registration completes". Probably the checkbox was clicked to send Email but the messages were not configured, resulting in blank Emails upon registration. | |
| |
|
Q:Why can't I complete test registrations because of invalid nameservers? | |
A:RSPs using the test environment can not register domain names through OpenSRS with many nameservers that otherwise exist "in the real world". This is a side-effect of the way that we have set up our test environment. The data set included in the RITE is minimal and does not include a comprehensive list of name servers. The production ("live") environment does refer to this information. While you are in the test environment, please feel free to use these nameservers: default.opensrs.org default2.opensrs.org Do not forget to change these settings prior to going live! | |
| |
|
Q:Why can/can't I register a name that's available/unavailable on the Internet? | |
A:RSPs using the Horizon test environment can register domain names through OpenSRS that are not available "in the real world", and some domains available in the Internet are registered on the testing environment. This is a side-effect of the way that we have set up our testing environment. The data set included in the RITE is minimal and does not include a comprehensive list of registered domains. While you are in the test-environment, please feel free to register any domain name you like. It's just for practice in an environment where you can work out potential bugs of your processes, and your mistakes won't cost anything. | |
| |
|
Q:Why can't I connect to horizon.opensrs.net with verify_install.cgi? | |
A:Here are some common issues which might cause you to be unable to authenticate with our test environment server: * Are you using the latest version of the OpenSRS client software scripts? We continue to support 2.0.x versions but we still recommend you use the latest version. * If possible, you should switch from Crypt:DES to Crypt:Blowfish as it is more stable and secure. (This is done in the OpenSRS.Conf file) * Have you regenerated your private key on the test environment Web interface? http://resellers-test.opensrs.net/ Select "Generate New Private Key" Copy-and-paste this alphanumeric string between the quotations marks of the PRIVATE_KEY variable of your OpenSRS.conf file. * Note: you can change this key and re-enter it into your OpenSRS.conf file at any time should you feel that it has been viewed by others. After you did the copy-and-paste, did you make sure there were no leading or trailing spaces within the quotation marks? :-) * Are there port restrictions on your server, or on your firewall? The older versions of the client scripts require access to ports 50000 and 51000. Versions 2.2 and above uses port 55000. Most servers don't block these (non-privileged) ports, but a paranoid firewall might. * Please note, the test environment (horizon.opensrs.net) does not check your server's IP address to authenticate - this is a security feature of the live environment (rr-n1-tor.opensrs.net) only. | |
| |
|
Q:Why do I get "unable to open socket" authenticating with verify_install.cgi? | |
A:Here are some common issues which might cause you to be unable to authenticate with our test environment server: * Are you using the latest version of the OpenSRS client software scripts? We continue to support 2.0.x versions but we still recommend you use the latest version. * If possible, you should switch from Crypt:DES to Crypt:Blowfish as it is more stable and secure. (This is done in the OpenSRS.Conf file) * Have you regenerated your private key on the test environment Web interface? http://resellers-test.opensrs.net/ Select "Generate New Private Key" Copy-and-paste this alphanumeric string between the quotations marks of the PRIVATE_KEY variable of your OpenSRS.conf file. * Note: you can change this key and re-enter it into your OpenSRS.conf file at any time should you feel that it has been viewed by others. After you did the copy-and-paste, did you make sure there were no leading or trailing spaces within the quotation marks? :-) * Are there port restrictions on your server, or on your firewall? The older versions of the client scripts require access to ports 50000 and 51000. Versions 2.2 and above uses port 55000. Most servers don't block these (non-privileged) ports, but a paranoid firewall might. * Please note, the test environment (horizon.opensrs.net) does not check your server's IP address to authenticate - this is a security feature of the live environment (rr-n1-tor.opensrs.net) only. | |
| |
|
Q:Why do the HTML files in the templates directory have {{CGI}} tags in them? | |
A:You're accessing HTML templates directly, and they are not meant to be used that way. They have metavariables in them like "{{CGI}}" that are replaced with global variables by the CGI scripts, based on the settings in the OpenSRS.conf file. | |
| |
|
Q:If I use reg_system.cgi, do I need to manually process each domain from the Pending queue using the Web interface? | |
A:No. There is an option under the "Tech Contact Information" link of our Web interface which allows you to specify immediate processing or processing manually. We recommend that you be absolutely sure you can secure payment from clients before attempting to have registrations processed immediately and without any human intervention. | |
| |
|
Q:What could be wrong if I am getting an "internal server error" on the scripts? | |
A:Some basic sanity checks for your configuration: * Check how you are permissioning the files and directories of the client software - are all permissions set the way you like, and in a way that works? There's no easy answer to how to set permissions your files (I could tell you to set permissions to 755, but that wouldn't apply to all possible situations). * Did you edit {YOURWEBPATH}/etc/OpenSRS.conf (or wherever you saved it) and set the variables appropriately for your configuration. OpenSRS.conf should also be executable. * Did you edit the CGI scripts in the {YOURWEBPATH}/cgi/ directory (manage.cgi, reg_system.cgi, verify_install.cgi) and set the variables for your configuration? These CGI scripts should also be executable. * The PERL code in {YOURWEBPATH}/lib should also be executable. Beyond this, see the Apache Web server question (if appropriate) for some links to Apache documentation. | |
| |
|
Q:What's the difference between register.cgi and reg_system.cgi? | |
A:reg_system.cgi is designed to be used with your existing credit card processing system. It also obeys all the flags set in your OpenSRS.conf file and your RSP account. This is commonly used when integrating the OpenSRS system with an existing web site. register.cgi is a "bare bones" version intended to be used as an example for programmers building their own version of the scripts. It ignores the "Process Immediately" flag and always registers domains instantly. It also lacks the "hooks" for integrating your credit card processing system. It should not be used without modification. The scripts are Open Source and are intended to be modified to suit your needs or to serve as example code as needed. Whether you implement reg_system.cgi or register.cgi, don't make either of them available and executable on your Web server unless you know what you're doing. This could potentially open up a security hole. | |
| |
|
Q:What policies have to have posted on my site in order to be an OpenSRS RSP? | |
A:OpenSRS requires the following policies to be posted at your site at all times: The ICANN Uniform Domain-Name Dispute-Resolution Policy. This can be found at: http://www.icann.org/udrp/udrp.htm You should use this link directly. Exhibit A of The OpenSRS RSP Agreement. Because different TLDs are run by different companies, every TLD requires a separate contract and Exhibit A. Some registries also have other special requirements. The complete list is on our web page. Exhibit A will have to be stored on your web server with your RSP info included. | |
| |