Changelog
v3.7.6
Released April 5th, 2023
Latest Version
Fixed log error when doing a contact update with trade (owner change).
Previous Versions
v3.7.5
Released February 15th, 2023
View/hide detailed changelog
IDNs now work for all operations
Fixed .FR issues
Fixed registrant verification bug
Fixed bug where domain forwarders were not added
Code compatible with WHMCS 8.61, PHP 8.1 and ioncube 12
v3.7
Released April 7th, 2017
View/hide detailed changelog
- Fixed domain sync bug when renewing expired domains
- Updated domain sync function
- Added ability to view domain notes
- Added ability to view registration verification status
- Added ability to resend registrant verification email
- Fixed bug with "Check transfer status" function
v3.6
Released March 31st, 2017
View/hide detailed changelog
- Fixed domain contact update using "Use Existing Contact" function
- Fixed toolkit bug on contact update
- Fixed registration bug on .CA domain names
- Fixed bug that duplicates the country code on phone numbers
- Fixed bug in ICANN trade process
v3.5.1
Released December 5th, 2016
View/hide detailed changelog
- Fixed auto unlock of domain names during updates
- Improved error handling and user message for functions SaveNameservers(), GetNameservers()
- Cleaned up module log reporting for functions getConnectData(), SaveNameservers(), ModifyRegistrarLock()
- Removed cookie use in function GetNameservers()
- Improved contact set validation for function SaveContactDetails()
v3.5
Released November 29th, 2016
View/hide detailed changelog
- Implemented new ICANN trade policy for all gTLDs (Review new ICANN policy above)
- Automated contact updates to all gTLDs by accepting Tucows Inc. as DA
- Registrant IP is logged with OpenSRS API server for ICANN audits on contact updates
- Improved multiple end user error messages
- Improved error handling for contact update function
v3.4
Released May 27th, 2016
View/hide detailed changelog
- Adds support and fixes the phone # formatting issue that affected WHMCS’ OpenSRS module
- Added support for an older version of PHP for the domain sync function
- .ORG TLD no longer requires an organization name
USA Domains @usa4038
Sad to see OpenSRS dropping the ball here. One would think they would want more hosts using them. Without good integration with WHMCS, I'm sure it will begin to toll on their business and bottom line. Users want to self manage, not place tickets. It would be in their bet interest to keep up with this over their new reseller portal.
Steven Craig @steven8924
This module is really bad now, including breaking the whmcs nightly cron when there are errors and the code runs the die() function.
Vote for WHMCS to include the remaining features into their own module that is supported:
https://requests.whmcs.com/idea/completed-needed-remaining-features-for-opensrs-module
John @john8834
disappointed is all I can say. at least give one last update before saying your not going to work on it anymore. unless the native one in WHMCS has improved significantly, its also useless, ah nope, it still doesnt allow dns management AND they have a warning that it doesnt work with php 7.2 on their site as well! @tallship what setup are you using then now for managing opensrs domains and dns services? modules garden modules seem overkill and overpriced for something that should be provided either by whmcs Or opensrs. thanks!
thanks
Bradley D. Thornton @tallship
Do not install this module unless you are running <= WHMCS 7.1 - and if you're running WHMCS 7.1, you're running an insecure instance that places your customers at risk.
This module (which as I understand it, is authored by ModulesGarden - not Tucows/OpenSRS) does not work with recent installations of WHMCS and PHP, and is therefore.... useless.
The good support representatives over at OpenSRS told me in no uncertain terms that this is an abandoned module.
Having said that, there are other OpenSRS modules for free that do most of the things this module does, including email, DNS (a proper, and "properly maintained" ModulesGarden module), certs, and other aspects that this module used to provide.
Another thing to remember, is that there is official OpenSRS domain registration services within WHMCS itself. just enable the module that is included with all releases of WHMCS. If you combine that with other 3rd party modules you can achieve the same level of functionality and much, much more.
I hope that helps!
.
Marco Camparsi @marco6976
WHMCS is one of the best solutions to automate Hosting, and domain registration, both from functionality and accounting and everything in between, best solution to setup and watch it make some money with little continued work, it is a shame that this addon doesn't work nor is it continued to be supported, due to this we will be moving away from OpenSRS and on to a different platform, but will continue using WHMCS, it will be a lot of work to bring domains from one to another, however it would be much more work to setup, and learn something different than WHMCS who is tried tested and true and never let us down. not sure what why OpenSRS made this decision, doesn't make sence to me, but again I don't have all the information they have, from my stand point it's a shame, and as a warning to other companies be ware of this!!
Jeff Walker @CyberBasement
OpenSRS support says they have no plans to update this extension to work with newer releases of WHMCS or PHP. I say go find another registrar. I just wish it wasn't a colossal PITA to transfer all of our domains.
Steve West @steve246
We've been a reseller of opensrs for over a decade and unfortunately due to no updates from opensrs whmcs addon, we're now looking to move to another provider. Opensrs used to be great offering various tools but their lack of keeping up w/ technology (like updating this addon to work in PHP 7.2 and 7.3) says a lot about them.
Ed S @eduardas7198
Still doesn't work with the latest php version. Please make it compatible with the latest version.
Lars-Erik @larserik3693
I recently turned on ipv6 for the domain running whmcs and it killed the opensrs pro plugin.
I've solved it by changing line 137 in opensrs/openSRS_base.php to:
$context = stream_context_create(array(
'socket' => array(
'bindto' => '0.0.0.0:0',
)));
$this->_socket = stream_socket_client($this->crypt_type . '://' . $this->osrs_host . ':' . $this->osrs_sslPort, $this->_socketErrorNum, $this->_socketErrorMsg, $this->_socketTimeout, STREAM_CLIENT_CONNECT, $context);
It will break on update, so it's not my preferred way of fixing it....
Bradley Porter @SaneChoice
I have to agree with Jason. The slowness to adopt the latest PHP and WHMCS versions means this module has unfulfilled potential. This means quite a lot of manual hacking to make it work if you want to ensure your WHMCS instance(s) is as secure as possible. When you contact OPENSRS support for an update, they just state they cannot provide one and thats it.
It is also worth noting that OpenSRS (now) do not offer you any form of a discount if you are a small player in the domain market. So, no cost differential and slow software updates now makes this a service we are moving away from.
Jason Agouris @iTristanJason
@OpenSRS the module works fine and when you release an upgrade it's generally always an improvement BUT your releases for WHMCS upgrades are WAY WAY too slow.
WHMCS is now at version 7.4 WHMCS coming out and OpenSRS support just told me that it "will be a few months" until the next upgrade. Months, still?!?! And no telling what version this will support.
Here is why this matters. This isn't only about OpenSRS, it's about the users' ecosystems *around* WHMCS – meaning the various tools, modules, plugins etc that OpenSRS users add to their business platforms to remain competitive, make more money, sell more domains, hosting services, etc etc to get clients in general. That ecosystem is expected to progress more or less at the same pace as WHMCS upgrades with some, but not lots of expected lag.
OpenSRS at the moment is firmly late to the game EVERY time now and it's making me see OpenSRS as firmly the weak link in our ecosystem because we have to keep holding back over and over waiting for your upgrades which seems to be getting even later to the game. This as compared to our other module partners, who are weeks to a couple of months, versus months to what's going to be nearly a year between upgrades.
You just need to understand that by making business partner-users wait *this* long we're now actually considering our ability to keep this up with OpenSRS long term from a business point of view. And we like you guys. Imagine those potential partners who couldn't care less?!
I'd give you 4 or 5 for the module, but I'm giving 2 for the upgrades – let's step it up guys!
Reggie Goldman @reggie8463
I've used it to transfer, register, edit records and contact information on v7.3 from the client area. It works fine. However there is a small amount of troubleshooting you may have to do and editing these files directly is not favorable. Please keep updating.
Thanks!
Jimmy Wells @wellshosting
to much bug
Ruben Chet @Ruben
No comment provided.
Blue Net Box @BlueNetBox
Overall, it works great and support is taking care of its users which is a plus.
However, there are too many native WHMCS files to edit (i.e. english language, domain fields and whois servers files). Every time WHMCS launches an update, we need to re-edit and append some OpenSRS text to those files over and over. It is counter-productive and time consuming.
I am sure there could be a way to add your own files somewhere without the need to edit a single WHMCS native file. Update this and your plugin will be awesome.
Jeff Walker @CyberBasement
EDIT: The fixes in version 3.7 indeed appear to fix the issues I reported below. Also included are a few nice enhancements added to the domain details display such as the verification status and ability to retrieve domain notes/history from OpenSRS. Upgrading rating to 4 stars.
The module is very buggy since the last release. Updating contact information using the account contact details no longer works. You must type all of the information for each contact into the form manually.
Also, after renewing a domain the due and expiration dates are incorrectly reset on the next sync. If not caught, the domain will be set to "expired" and the client will not be invoiced for the next renewal.
Support has been able to reproduce both of these issues but has been unwilling to fix them for several months. Do yourself a favor and just use a different registrar, unless you like spending lots of time manually entering data and double-checking all of your domains to make sure the info is accurate.
Michael Levine @OpenSRS
Hi Jeff,
Owner@OpenSRSWe've just published v3.7 which addresses both of the issues you've outlined here. If you have any further feedback, please feel free to reach out to our support team.
Warren Priestley @ukhostme
It's great to see an official module for OpenSRS that works with WHMCS v7+