[GH-ISSUE #6] Can't apply changes - loginKey 'priority' not an Integer or not present #4

New issue

Closed

opened 2026-02-26 10:35:24 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 10:35:24 +03:00

Owner

Originally created by @marnovdm on GitHub (Jan 20, 2016).
Original GitHub issue: https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/6

Running powerdns 3.4.1-4+deb8u3 on Debian 8 and latest version for PowerDNS-Admin console. I can login but when trying to apply changes (add record) I get this error: loginKey 'priority' not an Integer or not present. I noticed something about 'priority' in https://doc.powerdns.com/md/authoritative/upgrading/ but that's only in 3.4.2. Any idea what's going on? Logs show:

[INFO] 10.168.100.2 - - [20/Jan/2016 17:16:38] "POST /domain/mydomain.io/apply HTTP/1.1" 200 -
[ERROR] Cannot apply record changes.
[DEBUG] Key 'priority' not an Integer or not present

Thanks in advance, it looks like a really nice web ui so I hope we can use it!

EDIT: Exact frontend error: '{ "msg": "Key 'priority' not an Integer or not present", "status": "error" }'

Originally created by @marnovdm on GitHub (Jan 20, 2016). Original GitHub issue: https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/6 Running powerdns 3.4.1-4+deb8u3 on Debian 8 and latest version for PowerDNS-Admin console. I can login but when trying to apply changes (add record) I get this error: loginKey 'priority' not an Integer or not present. I noticed something about 'priority' in https://doc.powerdns.com/md/authoritative/upgrading/ but that's only in 3.4.2. Any idea what's going on? Logs show: [INFO] 10.168.100.2 - - [20/Jan/2016 17:16:38] "POST /domain/mydomain.io/apply HTTP/1.1" 200 - [ERROR] Cannot apply record changes. [DEBUG] Key 'priority' not an Integer or not present Thanks in advance, it looks like a really nice web ui so I hope we can use it! EDIT: Exact frontend error: '{ "msg": "Key 'priority' not an Integer or not present", "status": "error" }'

kerem referenced this issue

2026-02-26 10:35:24 +03:00

[GH-ISSUE #4] Able to create empty domains #6

kerem closed this issue

2026-02-26 10:35:24 +03:00

kerem commented

2026-02-26 10:35:25 +03:00

Author

Owner

@sirantd commented on GitHub (Jan 29, 2016):

Have same problem with all frontends i checked.

Looks like all using modern api, and all now work when i installed powedns 3.4.7 from jessie-backports

Add to /etc/apt/sources.list
deb http://http.debian.net/debian jessie-backports main

apt-get update
apt-get install -t jessie-backports pdns-server (and all other backends, etc)

restart pdns service

@sirantd commented on GitHub (Jan 29, 2016): Have same problem with all frontends i checked. Looks like all using modern api, and all now work when i installed powedns 3.4.7 from jessie-backports Add to /etc/apt/sources.list deb http://http.debian.net/debian jessie-backports main apt-get update apt-get install -t jessie-backports pdns-server (and all other backends, etc) restart pdns service

kerem commented

2026-02-26 10:35:25 +03:00

Author

Owner

@marnovdm commented on GitHub (Feb 1, 2016):

@sirantd thanks, that seems to work! I thought I checked the backports version but I guess I didn't :)

@marnovdm commented on GitHub (Feb 1, 2016): @sirantd thanks, that seems to work! I thought I checked the backports version but I guess I didn't :)