You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/provider/inwx.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ You will hit this limitation in the following two scenarios:
29
29
* You use INWX as both the registrar and the DNS provider. In this case, DNSControl will try to login twice too quickly and the second login will fail because a TOTP code will be reused. The only way to support this configuration is to use a INWX account without two-factor authentication.
30
30
31
31
If you cannot work around these two limitation it is possible to create and manage sub-account - with specific permission sets - dedicated for API access with two-factor
32
-
authentication disabled. This is possible at [inwx.de/en/account](https://www.inwx.de/en/account).
32
+
authentication disabled. This is possible at [inwx.de/de/customer/login](https://www.inwx.de/de/customer/login).
33
33
34
34
If two-factor authentication has been enabled you will also need to provide a valid TOTP number.
35
35
This can also be done via an environment variable:
0 commit comments