IP Update - Bad Auth
IP Update - Bad Auth
- Casa
- Pannello di controllo
- Forum della Comunità
- Services
- Dynamic DNS Service
- IP Update - Bad Auth
- Forum della Comunità
- IP Update - Bad Auth
Argomento: IP Update - Bad Auth
I have been trying to run the IP updater for HOURS. I have changed my password several times, each time logging out of the control panel and then logging back in, to make sure it is correct as I am changing both passwords together. I know my username is correct as well. I'm about to lose my mind... Help please?
Rispondi con citazione | Segnalare
Check the location name. If you assigned your domain name a location name in the control panel, you need to use that location name in the IP update client as well.
Rispondi con citazione | Segnalare
jdidi wrote:Check the location name. If you assigned your domain name a location name in the control panel, you need to use that location name in the IP update client as well.
Rispondi con citazione | Segnalare
While trying to update A record for a single dynamic host:
md5_pass = Digest::MD5::md5(passwd) // BADAUTH
md5_pass = Digest::MD5::md5_hex(passwd) // BADAUTH
md5_pass=$(echo -n pass |md5sum // BADAUTH
md5_pass=$(echo -n pass |openssl dgst -md5) //BADAUTH
# each of the above that uses echo , tried again with shell printf
# each of the above outputs compared with other methods of generating the same output
// BADAUTH in all cases
# each of the above methods substituted sha256 for md5, // BADAUTH
# tried with and without user name (since documents suggest username is optional: // BADAUTH
# tried base64 since documents mention base64 // BADAUTH
# tried re-encoding prevous outputs as base64 // BADAUTH
# tried hexdump() and od -c looking for extraneous linefeeds, all inputs are single quoted
// BADAUTH
# requested diagnostic feedback from a short lifetime one time password feature so that the encoded
request could be compared with what the interface is comparing it to for the password, waiting to hear back
md5_pass = Digest::MD5::md5(passwd) // BADAUTH
md5_pass = Digest::MD5::md5_hex(passwd) // BADAUTH
md5_pass=$(echo -n pass |md5sum // BADAUTH
md5_pass=$(echo -n pass |openssl dgst -md5) //BADAUTH
# each of the above that uses echo , tried again with shell printf
# each of the above outputs compared with other methods of generating the same output
// BADAUTH in all cases
# each of the above methods substituted sha256 for md5, // BADAUTH
# tried with and without user name (since documents suggest username is optional: // BADAUTH
# tried base64 since documents mention base64 // BADAUTH
# tried re-encoding prevous outputs as base64 // BADAUTH
# tried hexdump() and od -c looking for extraneous linefeeds, all inputs are single quoted
// BADAUTH
# requested diagnostic feedback from a short lifetime one time password feature so that the encoded
request could be compared with what the interface is comparing it to for the password, waiting to hear back
Rispondi con citazione | Segnalare
Autore | Argomento: IP Update - Bad Auth |
---|---|
scotntam Iscritto: 19/12/2017 |
IP Update - Bad Auth giovedì 10 maggio 2018 07:27
I have been trying to run the IP updater for HOURS. I have changed my password several times, each time logging out of the control panel and then logging back in, to make sure it is correct as I am changing both passwords together. I know my username is correct as well. I'm about to lose my mind... Help please?
|
jdidi Iscritto: 23/06/2017 |
IP Update - Bad Auth martedì 15 maggio 2018 09:38
Check the location name. If you assigned your domain name a location name in the control panel, you need to use that location name in the IP update client as well.
|
engsysmon Iscritto: 26/12/2021 |
IP Update - Bad Auth martedì 4 gennaio 2022 07:14
|
engsysmon Iscritto: 26/12/2021 |
IP Update - Bad Auth martedì 4 gennaio 2022 07:24
While trying to update A record for a single dynamic host:
md5_pass = Digest::MD5::md5(passwd) // BADAUTH md5_pass = Digest::MD5::md5_hex(passwd) // BADAUTH md5_pass=$(echo -n pass |md5sum // BADAUTH md5_pass=$(echo -n pass |openssl dgst -md5) //BADAUTH # each of the above that uses echo , tried again with shell printf # each of the above outputs compared with other methods of generating the same output // BADAUTH in all cases # each of the above methods substituted sha256 for md5, // BADAUTH # tried with and without user name (since documents suggest username is optional: // BADAUTH # tried base64 since documents mention base64 // BADAUTH # tried re-encoding prevous outputs as base64 // BADAUTH # tried hexdump() and od -c looking for extraneous linefeeds, all inputs are single quoted // BADAUTH # requested diagnostic feedback from a short lifetime one time password feature so that the encoded request could be compared with what the interface is comparing it to for the password, waiting to hear back |
Al momento è lunedì 23 dicembre 2024 12:48 US Mountain Standard Time
lunedì 23 dicembre 2024 12:48