`ERROR getting record IDs: HTTP status is not valid: 403` with Porkbun #919

poperigby · 2025-01-22T01:28:28Z

poperigby
Jan 22, 2025

This is my configuration:

{
  "settings": [
    {
      "provider": "porkbun",
      "domain": "haddock.cc",
      "api_key": "pk1_REDACTED",
      "secret_api_key": "sk1_REDACTED"
    }
  ]
}

I'm getting this log output:

WARN cannot DNS resolve .haddock.cc after 5 tries: lookup .haddock.cc: no such host
INFO IP address of .haddock.cc is invalid IP and your IP address  is 75.172.41.92
INFO Updating record [domain: haddock.cc | host:  | provider: porkbun | ip: ipv4 or ipv6] to use 75.172.41.92
ERROR getting record IDs: HTTP status is not valid: 403: <html><head><title>403 Forbidden</title></head><body><center><h1>403 Forbidden</h1></center></body></html>

Version: 2.9.0

jezh42 · 2025-02-21T15:15:14Z

jezh42
Feb 21, 2025

I believe this is a bug with not using the new API hostname. DDNS-Updater is still using "porkbun.com" and needs to use "api.porkbun.com". Documenation for reference: https://porkbun.com/api/json/v3/documentation#apiHost
Opened a new issue regarding this #943

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

`ERROR getting record IDs: HTTP status is not valid: 403` with Porkbun #919

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Uh oh!

ERROR getting record IDs: HTTP status is not valid: 403 with Porkbun #919

Uh oh!

poperigby Jan 22, 2025

Replies: 1 comment

Uh oh!

Uh oh!

jezh42 Feb 21, 2025

`ERROR getting record IDs: HTTP status is not valid: 403` with Porkbun #919

poperigby
Jan 22, 2025

jezh42
Feb 21, 2025