Contact Information
No response
1Panel Version
v2.1.12
Problem Description
After updating to 1Panel v2.1.12, I am unable to add an OVH DNS account. When I attempt to create a new DNS account, the form does not show the required fields for OVH (Application Key, Application Secret, Consumer Key). Instead, only generic fields are displayed: Name, Type, Endpoint, and AccessToken.
Native OVH support was introduced in v2.0.12, and according to the documentation, selecting "OVH" as the Type should dynamically reveal the three key fields and an endpoint selector. This is not happening.
As a result, I cannot use my OVH API credentials (which consist of three separate keys) because there is no place to enter them.
Steps to Reproduce
- Install or update 1Panel to version v2.1.12.
- Go to Websites → Certificates → Manage DNS providers.
- Click Create.
- In the Type dropdown, select OVH.
- After selecting OVH, the form does not update. Only the default fields remain visible: Name, Type, Endpoint, and AccessToken. The expected fields for Application Key, Application Secret, and Consumer Key do not appear.
- It is therefore impossible to save a valid OVH DNS account, because the three required API keys cannot be entered.
(OVH application "fff" is show OVHcloud createToken and this API is removed after make screenshot)
The expected correct result
When "OVH" is selected as the DNS provider type, the form should update to show:
- Application Key
- Application Secret
- Consumer Key
- Endpoint (dropdown with ovh-eu / ovh-ca)
This would allow users to enter the three OVH API credentials required for DNS-01 challenge automation.
Related log output
Additional Information
No response
Contact Information
No response
1Panel Version
v2.1.12
Problem Description
After updating to 1Panel v2.1.12, I am unable to add an OVH DNS account. When I attempt to create a new DNS account, the form does not show the required fields for OVH (Application Key, Application Secret, Consumer Key). Instead, only generic fields are displayed: Name, Type, Endpoint, and AccessToken.
Native OVH support was introduced in v2.0.12, and according to the documentation, selecting "OVH" as the Type should dynamically reveal the three key fields and an endpoint selector. This is not happening.
As a result, I cannot use my OVH API credentials (which consist of three separate keys) because there is no place to enter them.
Steps to Reproduce
(OVH application "fff" is show OVHcloud createToken and this API is removed after make screenshot)
The expected correct result
When "OVH" is selected as the DNS provider type, the form should update to show:
This would allow users to enter the three OVH API credentials required for DNS-01 challenge automation.
Related log output
Additional Information
No response