Closed hendranata closed 4 years ago
yes we can disable invoice from SSLCENTER module.. (then the invoice only appear once , that is from WHMCS) but i prefer to use invoice generated from SSLCENTER module.. not from WHMCS .. any idea?
We are checking that with developers now
okay any update?
Blocking the generation of invoices by WHMCS, is very problematic, the easiest way to avoid this is to change the Next Due Date for the service. Then we will be able to delay the invoice generation by WHMCS, and after paying the invoice generated by the module, the service will be canceled, so subsequent invoices for it will never be generated again. Remember, however, that in this case, you must ensure that invoicing is set correctly so that the module always generates an invoice faster than WHMCS. Are you satisfied with this solution?
how do we change the next due date? i hope it can be done automatically.. not change manually for every ssl product/service. thanks..
assume the user does not want to extend the service..then the invoice will be double right? i hope any other best solution.. not like this a bit tricky..
I think this is so dumb. If we use the built-in function to create invoices, we must make sure that the client pays for their invoice (which ironically has identical invoice date and due date) 14 days before the due date in WHMCS - if they don't WHMCS will create a new one, meaning the client has double invoices for the same product. We can't really expect clients to pay for their products before the renewal is actually due.
Something really needs to be done about this, or we'll need to find another provider for SSL certificates :-/
I think this is so dumb. If we use the built-in function to create invoices, we must make sure that the client pays for their invoice (which ironically has identical invoice date and due date) 14 days before the due date in WHMCS - if they don't WHMCS will create a new one, meaning the client has double invoices for the same product. We can't really expect clients to pay for their products before the renewal is actually due.
Something really needs to be done about this, or we'll need to find another provider for SSL certificates :-/
Do you have a suggested scenario of how that should work? Please share
Hello,
I not really understand why need this separate invoice creating method. Whats wrong with WHMCS built in invoice creating stuff? It create the invoice when admin configure (before X days of due date). After when client pay the invoice, i see two way: module cancel the existing ssl service, and create a new one, without creating invoice. User can configure it, etc,etc. Other way is, to update the API id for the existing service to the new order API, and client see its status in client area.
In our env, (i not really know how we conigure it), the second thing working, expect we have to update remoteAPI manually. But basically the module create a new order in gogetssl system with the existing CSR, client receive the validation email accept it and they give the new cert.
Do you have a suggested scenario of how that should work? Please share
Don't have the module create the invoice. Only use the invoice created by WHMCS. When a client pays for an invoice for renewal of SSL, use a hook to create a new identical product for the client for the new certificate.
If possible (I really don't know if it is), have WHMCS generate invoices for SSL certificates x-amount of days before (this value could be saved in a table in the database). I know that this might not be possible due to the way WHMCS works, but it's worth investigating.
We're depending too much on the client renewing the certificate way before renewal is actually due right now.
Other way is, to update the API id for the existing service to the new order API, and client see its status in client area.
This would not allow the client to reissue the old certificate after renewing, though. It might be needed in some cases.
thank you, your help appreciated. we will investigate
Why they have to reissue that? When renewal certificate geretated old cert will be revoked.
"
Hello, I not really understand why need this separate invoice creating method. Whats wrong with WHMCS built in invoice creating stuff? It create the invoice when admin configure (before X days of due date). After when client pay the invoice, i see two way: module cancel the existing ssl service, and create a new one, without creating invoice. User can configure it, etc,etc. Other way is, to update the API id for the existing service to the new order API, and client see its status in client area. In our env, (i not really know how we conigure it), the second thing working, expect we have to update remoteAPI manually. But basically the module create a new order in gogetssl system with the existing CSR, client receive the validation email accept it and they give the new cert.
The thing is that customers should have control for both orders, NEW, and renewal as its different SSL certificates.
SCENARIO 1: Customer renewed SSL in 80-days before expiration, he got new SSL, but he wants to reissue previous to a different domain name for just 80-days, that would be impossible. We know there are such clients, they don't want to order trial certs for that.
SCENARIO 2 (most common): Lets say customer renew EV SSL, it would take time 5-10 days, during that period, the customer may need to reissue SSL for lost KEY or to modify SAN items. The new cert not ready yet, but control to existing will be lost.
SCENARIO 3: Customer renewed SSL, but wants to revoke previous one, he will be not able to do that without control. Please understand, every renewal is just new SSL, having no connection to the old one, they will work simultaneously.
SCENARIO 4: The customer had SHA/RSA SSL in the past and wants to Renew with ECC now, but keeping RSA/SHA for a transition period, again, if he lost a key or need just to reissue original SSL he will be not able to do that.
Ah, you're quite right, @charliehu - I didn't think about that. The new certificate will cover the remaining time for the old certificate. Your idea actually might just work better than what I suggested. Use the API to create a new certificate with GGSSL, then update the ID in WHMCS to the corresponding order.
so any solution the best for this case? i still no idea about this module issue. hope u can fix soon
We are checking with MG the option to remove own invoicing and using built-in WHMCS one. At present we do not have clear vision why separate invoicing were created. Maybe they know the reason
in whmcs product/service, there is an option called: Recurring Cycles Limit by default it set to 0 means unlimited recurring until they cancel the service. if we set value 1, it means there is no renewal invoice or the renewal appear only once?
does it help us to prevent double invoice in the next renewal? so we encourage the client to purchase new one instead of renew the invoice.
double invoice makes the user confused sometime.. or they might pay twice unconsciously
@vlad-evg
SCENARIO 1:
Why they do this? I not see any provider who send renewal invoice 80 days before service due date. Usually it sent 14-7 days before the expiration date.
SCENARIO 2:
We have only few hundred cert, but newer met with this scenario. I mean if somebody lost they key within this short timefrime. But, this 5-10 day time is only valid for cert type where need to check documents manually. For domain validated certificates not need more than 5 min.
SCENARIO 3:
I not see revoke API command (https://github.com/gogetssl/api/wiki) - or even button for this in GOGETSSL admin porta, so for revoke client have to open ticket. I don't know if this is a free for all kind of cert even.
SCENARIO 4:
But he can reissue the new certificate using WHMCS client area
@vlad-evg
SCENARIO 1:
Why they do this? I not see any provider who send renewal invoice 80 days before service due date. Usually it sent 14-7 days before the expiration date.
SCENARIO 2:
We have only few hundred cert, but newer met with this scenario. I mean if somebody lost they key within this short timefrime. But, this 5-10 day time is only valid for cert type where need to check documents manually. For domain validated certificates not need more than 5 min.
SCENARIO 3:
I not see revoke API command (https://github.com/gogetssl/api/wiki) - or even button for this in GOGETSSL admin porta, so for revoke client have to open ticket. I don't know if this is a free for all kind of cert even.
SCENARIO 4:
But he can reissue the new certificate using WHMCS client area
S1. The standard procedure to renew SSL is 90-days before expiration. It was like that for ages. We have a situation when OV/EV renewal takes 90+ days for some difficult regions and customers.
S2. That is sad correctly, you have a few hundred, while we operating more than 1,1mil certs and face different scenarios and it is hard to cover issues to make all happy. Yes, 5 minutes for DV certs, but it can be SAN SSL, and the customer doesn't have enough time to replace cert on 10 servers overnight, they want control under both certs due to own security reasons etc... :/ Trust me, there are weird customers and cases.
S3. It is free for all kind of certs. It is in API, but not included to WHMCS one, just for custom resellers. We are building new system, where you will be able to see all certs, serial numbers, statuses and will be able to revoke historical certs
S4. Yes, he can and SHOULD, but... we have to deal with different customers and their problems. You are an advanced user and have a proper vision of situation, but again, not all are your level and of course some just have specific rules.
*** Please note, starting at March 2020 there will be no more 2yr SSL certs, the max will be 15 months (1yr actually), soon certs could be merged with domain period and many things could be easier
SCENARIO 1:
We spoke about WHMCS right? Nobody configure 90 days in WHMCS, becase of monthly services. Even the default is 14 days: https://docs.whmcs.com/Invoicing_Setup#Automatic_Invoice_Generation
SCENARIO 2:
Yes i know, you sell millons of SSL certificate. But this is a WHMCS module, so doesnt matter the procedure for big resellers with own system etc. You see the statistics, but i guess costumers who selling shared hosting and similar stuffs with WHMCS, mostly selling DVC certificates.
SCENARIO 3: Please tell me the relavent API request, i not find it in the documentation: https://github.com/gogetssl/api/wiki I think, unpublished, closed API request doesnt count in this case.
SCENARIO 4: You ,the developer/owner of this module doesnt have vision. There is multiple solution now, but all have some issue. At least have one properly working and documented solution, and vision.
SCENARIO 1:
We spoke about WHMCS right? Nobody configure 90 days in WHMCS, becase of monthly services. Even the default is 14 days: https://docs.whmcs.com/Invoicing_Setup#Automatic_Invoice_Generation
SCENARIO 2:
Yes i know, you sell millons of SSL certificate. But this is a WHMCS module, so doesnt matter the procedure for big resellers with own system etc. You see the statistics, but i guess costumers who selling shared hosting and similar stuffs with WHMCS, mostly selling DVC certificates.
SCENARIO 3: Please tell me the relavent API request, i not find it in the documentation: https://github.com/gogetssl/api/wiki I think, unpublished, closed API request doesnt count in this case.
SCENARIO 4: You ,the developer/owner of this module doesnt have vision. There is multiple solution now, but all have some issue. At least have one properly working and documented solution, and vision.
S1. You have own vision when you say "nobody" you operate on own experience. I would just say that features from screenshot are not just for fun. We paid for them to MG, because we got many requests for that: https://www.screencast.com/t/2Vc7QETmvKqM
S2. You can't image how many people use WHMCS to sell OV/EV certs :) Even large resellers don't want to have customer integrations and just use WHMCS as its simple and quick. Moreover, there are many agents, who resell via phone number and use WHMCS as billing, only for SSL, without domains and hosting. I would say module used by 60% of hosters and 40% others.
S3. API v2 is available and at present working for few custom clients. Yes, it is unpublished at present, and we can not count here on it. Sorry if it confused you
S4. At present we are trying to make changes suitable for all. If technically possible to use only WHMCS invoicing and no need to use custom, then we would remove than 100%.
any update guys??
Yes, we have solution and need to ask if that suits all of you.
So we would kill custom invoicing by the SSL addon keeping the logics of WHMCS billing.
So, in this case, the best solution would be to add a new option in the settings of the module Renew - New Order.
When this field is checked, a new order will be created for the client and the client will be able to reconfigure certificate.
If this field is not checked, the current certificate will only be renewed without a new order (overwrited) and all data will be automatically sent to our API.
What do you all think?
Hope u can release soon
Sent from Yahoo Mail for iPhone
On Tuesday, October 1, 2019, 3:56 PM, Vladislavs Dovoreckis notifications@github.com wrote:
Yes, we have solution and need to ask if that suits all of you.
So we would kill custom invoicing by the SSL addon keeping the logics of WHMCS billing.
So, in this case, the best solution would be to add a new option in the settings of the module Renew - New Order.
When this field is checked, a new order will be created for the client and the client will be able to reconfigure certificate.
If this field is not checked, the current certificate will only be renewed without a new order (overwrited) and all data will be automatically sent to our API.
What do you all think?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
So that option would work for you?
@charliehu, @DennisSkov will that also works for you?
Hi @vlad-evg That sounds exactly what we asked for! That would, in my opinion, be the best way to fix the current issues :)
If this field is not checked, the current certificate will only be renewed without a new order (overwrited) and all data will be automatically sent to our API.
Just to be clear: If the field is not checked, the certificate will renew on the existing order, right?
If not checked, the user still able to renew their ssl certificate but cant do reconfig? Do they need validate the domain ssl again?
Sent from Yahoo Mail for iPhone
On Tuesday, October 1, 2019, 4:11 PM, hendranata saputra hendranatas@yahoo.com wrote:
Hope u can release soon
Sent from Yahoo Mail for iPhone
On Tuesday, October 1, 2019, 3:56 PM, Vladislavs Dovoreckis notifications@github.com wrote:
Yes, we have solution and need to ask if that suits all of you.
So we would kill custom invoicing by the SSL addon keeping the logics of WHMCS billing.
So, in this case, the best solution would be to add a new option in the settings of the module Renew - New Order.
When this field is checked, a new order will be created for the client and the client will be able to reconfigure certificate.
If this field is not checked, the current certificate will only be renewed without a new order (overwrited) and all data will be automatically sent to our API.
What do you all think?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
When the new module release?
Sent from Yahoo Mail for iPhone
On Tuesday, October 1, 2019, 4:21 PM, hendranata saputra hendranatas@yahoo.com wrote:
If not checked, the user still able to renew their ssl certificate but cant do reconfig? Do they need validate the domain ssl again?
Sent from Yahoo Mail for iPhone
On Tuesday, October 1, 2019, 4:11 PM, hendranata saputra hendranatas@yahoo.com wrote:
Hope u can release soon
Sent from Yahoo Mail for iPhone
On Tuesday, October 1, 2019, 3:56 PM, Vladislavs Dovoreckis notifications@github.com wrote:
Yes, we have solution and need to ask if that suits all of you.
So we would kill custom invoicing by the SSL addon keeping the logics of WHMCS billing.
So, in this case, the best solution would be to add a new option in the settings of the module Renew - New Order.
When this field is checked, a new order will be created for the client and the client will be able to reconfigure certificate.
If this field is not checked, the current certificate will only be renewed without a new order (overwrited) and all data will be automatically sent to our API.
What do you all think?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Finally, it is released now, however, we are doing some tests, and clarifying information with MG.
do we need to do migrate? can u give me the tutorial migrate from previous version?
in this case, i want the generated invoice originally from whmcs module (not gogetssl module), then after they paid the invoice, it will create new service/product to particular user, so that they able to perform renew and validate their own ssl.. what is the best setting/config for that case? need a guide.. thanks
Please wait, some bugs related to latest release founded and we are still checking.
Okay also please answer my previous question
Sent from Yahoo Mail for iPhone
On Thursday, October 17, 2019, 6:10 PM, Vladislavs Dovoreckis notifications@github.com wrote:
Please wait, some bugs related to latest release founded and we are still checking.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
when the stable version release? so strange..
After long testings and analysis, we requested developers to make one final change to logics related to renewal.
Here is an Example#1: 1) Settings: YES: Automatic processing of renewal orders SELECT: "New Order" OR "Use existing order" Where "USE EXISTING" Selected
In that case, during renewal, the module would send the order to renewal with all the same data but would overwrite the same existing order. No new order will be created
Example#2: 1) Settings: YES: Automatic processing of renewal orders SELECT: "New Order" OR "Use existing order" Where "NEW Order" Selected
In that case, during renewal, the module would send the order to renewal with all the same data but would CREATE NEW ORDER for that. There will be 2 orders in the WHMCS, old and new
Example#3: 1) Settings: NO: Automatic processing of renewal orders SELECT: "New Order" OR "Use existing order" Where "Use existing order" Selected
In that case, the same/original order will be reset to "Configure" and the customer will need to submit new data manually
Example#4: 1) Settings: NO: Automatic processing of renewal orders SELECT: "New Order" OR "Use existing order" Where "NEW Order" Selected
In that case, the new order with the "CONFIGURE" status will be created. The customer would need to configure a new order. Old and new orders will be available
in that case, it would solve all issues (we hope so). Any comments are more then welcome, as we still have few hours before developers would start
Can you add, please, what will happen with WHMCS invoices in each case? How are they related to the ggetssl module orders?
once release, can u please provide clear documentation for those options..
once release, can u please provide clear documentation for those options..
YES, that is what are going to do, to make a clear and detailed documentation as the method has multiple settings.
Can you add, please, what will happen with WHMCS invoices in each case? How are they related to the ggetssl module orders?
In all cases, new Invoice will be created. Once it will be paid it will trigger module to do next steps
In all cases, new Invoice will be created. Once it will be paid it will trigger module to do next steps
Yeah, that's clear. The question is that how will relate the invoice generated by the SSLCENTER module order to the invoice generated by the whmcs itself?
Let me explain with an example.
Settings: SSL product is set as Recurring Invoice generation is set to 30 days (whmcs - Setup - Automation Settings) SSLCENTER module Settings set to "Recurring orders" - Enabled - Create automatical renewal invoice - 30 days
Will in this case both of them generate invoices?
What if they are set to generate invoices in different time periods (whmcs 30 days, module 15 days)? What if the SSLCENTER invoice generation is disabled?
No, the invoice will be generated by WHMCS only, not by module anymore.
It was not our idea to make invocing by the module, and now that should be removed
No, the invoice will be generated by WHMCS only, not by module anymore.
It is good to hear that, we have generated lot of false double orders because of this. Will it change anything if the product is set to 'One Time' instead of 'Recurring'?
any update?
I also would like to know if there is any news related to this change.
Sorry for the delay, we hope new release will be available within just few days with full explanations of how properly set all SSL addon
An automatic renewal attempt was triggered for this service but failed. The renewal will not be attempted again automatically. Please resolve the error and try again.
Why this coming?
Admin taken order and accepted it as client will pay later. SSL activated and installed and now once invoice paid after 3 days. This email received by admin? How to fix this issue?
From
Sunil YFounder & Cloud Solution Architect ----------------------------------------------------------------------- Tel. +91 9967222267 / 09300670068
https://members.w3services.net/viewticket.php?tid=233326&c=JBbCobNW&feedback=1
On Thu, Nov 21, 2019 at 2:12 PM Vladislavs Dovoreckis < notifications@github.com> wrote:
Sorry for the delay, we hope new release will be available within just few days with full explanations of how properly set all SSL addon
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gogetssl/whmcs-addon/issues/59?email_source=notifications&email_token=AHVPSUK2PU3PPEAPPSVJQ5TQUZCZFA5CNFSM4ISJMOSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEZNK7A#issuecomment-556979580, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHVPSUJ73DEO65RGVBOMZHLQUZCZFANCNFSM4ISJMOSA .
Let us urgently route that to Modules Garden
helo i am using latest version of gogetssl module for my whmcs 7.7.1
in this case if the ssl is going to be expired maybe in the next 3 months.. then system will generate new invoice for it. since i have enable "Create automatical renewal invoice" from the SSLCENTER module settings.
but whmcs also generate a new invoice as well 14 days before the ssl expired (i have set every 14 days before expired, whmcs will generate renew invoice)..
so, it means i will receive 2 invoice.. 1 from SSLCENTER , and another one from WHMCS system.. how to avoid that? thanks