Comments (9)
DL6ER
commented on August 16, 2024
1
Okay, I think we are getting there now. Yes, there is no way for the GUI to be notified instantaneously if a third-party application uses the API to disable blocking. Instead, the GUI pulls the status every ten seconds. Now I do indeed see that there is a bug in the GUI code because even when a timer is set, it is not applied. This will be fixed by pi-hole/web#2917
from ftl.
DL6ER
commented on August 16, 2024
I cannot confirm this. What I tried:
POST https://pi.hole/api/dns/blocking
Payload:
{"blocking":false,"timer":10}Response:
{"blocking":"disabled","timer":10,"took":0.017992973327636719}Then about one second later, I tried
GET https://pi.hole/api/dns/blocking
Response
{"blocking":"disabled","timer":8.9000000000000039,"took":9.5605850219726562e-05}and then roughly ten seconds later again
GET https://pi.hole/api/dns/blocking
Response:
{"blocking":"enabled","timer":null,"took":7.31945037841797e-05}So ... this seems to be correct? Do you get any timer when you do a GET request after sending your payload as above?
from ftl.
akordowski
commented on August 16, 2024
When I'm sending this payload
{ "sid": "...", "blocking": false, "timer": 10 }I get this response
{ "blocking": "disabled", "timer": null, "took": 6.6995620727539062e-05 }and also in the UI the blocking is disabled indefinetly.
I am testing it with the latest Docker development-v6 image on a Raspberry Pi.
from ftl.
DL6ER
commented on August 16, 2024
I saw you first had time instead of timer, are you sure there is no typo in your payload? If not, please enable debug.api (can e.g., be done on the web interface -> all settings) and show us what /var/log/pihole/FTL.log reveals when you submit your payload.
We expect to see either:
No change in blocking mode, resetting timer
or
Enabled/Disabled Pi-hole, timer set to ... seconds
where -1 seconds means that any of the three conditions below are not met in the request payload.
I did just try it with the development-v6 versions and just clicked on the web interface:
Also this worked exactly as expected. So I went to the source code of the API and checked what is going on and everything seems fine. Note that FTL will NOT complain if there is any typo (e.g., timrr) but simply ignore everything that is there and does not match to anything FTL knows about. This is necessary to support some obscure proxies that seem to add additional stuff into JSON payloads (like original client IP, etc.) so not something we can easily enforce.
The source code takes this number if these three are all true:
timeris present and written exactly like this (case-sensitive)- it is a JSON number, e.g.,
"300"is invalid - The value needs to be larger than zero.
from ftl.
akordowski
commented on August 16, 2024
I tested it again and it seams to work as expected:
But the GUI show still:
The FTL.log shows that for GET /api/dns/blocking now payload is received, which might be the reason why the timer in the GUI is not shown.
2023-12-27 19:55:03.707 [160/T167] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:55:03, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:55:03.707 [160/T167] DEBUG_API: Processing GET /api/info/sensors in /api/info/sensors
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:55:03, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Processing GET /api/info/system in /api/info/system
2023-12-27 19:55:03.708 [160/T167] DEBUG_API: Done
2023-12-27 19:55:03.708 [160/T169] DEBUG_API: Done
2023-12-27 19:55:04.388 [160/T172] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:55:04.388 [160/T172] DEBUG_API: Received no payload
2023-12-27 19:55:04.388 [160/T172] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:55:04.389 [160/T172] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:55:04, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:55:04.389 [160/T172] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:55:04.389 [160/T172] DEBUG_API: Done
from ftl.
akordowski
commented on August 16, 2024
Here the whole log
pi:/var/log/pihole# cat FTL.log
2023-12-27 19:52:22.134 [160/T167] DEBUG_API: Requested API URI: 192.168.0.1 -> POST /api/dns/blocking ? (null) (Content-Type application/json)
2023-12-27 19:52:22.134 [160/T167] DEBUG_API: Received payload with size: 85
2023-12-27 19:52:22.134 [160/T167] DEBUG_API: Read sid="*****" from payload (JSON)
2023-12-27 19:52:22.135 [160/T167] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:52:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:52:22.135 [160/T167] DEBUG_API: Processing POST /api/dns/blocking in /api/dns/blocking
2023-12-27 19:52:22.154 [160/T167] INFO: Config file written to /etc/pihole/pihole.toml
2023-12-27 19:52:22.154 [160/T167] DEBUG_API: Disabled Pi-hole, timer set to 300.000000 seconds
2023-12-27 19:52:22.154 [160M] INFO: Received SIGHUP, flushing cache and re-reading config
2023-12-27 19:52:22.155 [160M] INFO: Blocking status is disabled
2023-12-27 19:52:22.155 [160/T167] DEBUG_API: Done
2023-12-27 19:52:22.223 [160/T161] INFO: Compiled 1 allow and 3 deny regex for 6 clients in 19.0 msec
2023-12-27 19:52:55.476 [160/T172] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type application/json)
2023-12-27 19:52:55.476 [160/T172] DEBUG_API: Received payload with size: 40
2023-12-27 19:52:55.476 [160/T172] DEBUG_API: Read sid="*****" from payload (JSON)
2023-12-27 19:52:55.476 [160/T172] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:52:55, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:52:55.476 [160/T172] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:52:55.477 [160/T172] DEBUG_API: Done
2023-12-27 19:53:22.540 [160/T170] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/ftl ? (null) (Content-Type (null))
2023-12-27 19:53:22.541 [160/T170] DEBUG_API: Received no payload
2023-12-27 19:53:22.541 [160/T170] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.541 [160/T170] DEBUG_API: API Authentication: FAIL (CSRF token mismatch, received "3HRQdeu6DzBNpWNbVTm3xQ=", expected "4xf2NqgNVVPs/A7puQ4OqA=")
2023-12-27 19:53:22.541 [160/T170] WARNING: API: Unauthorized
2023-12-27 19:53:22.542 [160/T166] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/version ? (null) (Content-Type (null))
2023-12-27 19:53:22.542 [160/T168] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/system ? (null) (Content-Type (null))
2023-12-27 19:53:22.542 [160/T168] DEBUG_API: Received no payload
2023-12-27 19:53:22.543 [160/T173] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/messages/count ? (null) (Content-Type (null))
2023-12-27 19:53:22.543 [160/T168] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.543 [160/T173] DEBUG_API: Received no payload
2023-12-27 19:53:22.543 [160/T168] DEBUG_API: API Authentication: FAIL (CSRF token mismatch, received "3HRQdeu6DzBNpWNbVTm3xQ=", expected "4xf2NqgNVVPs/A7puQ4OqA=")
2023-12-27 19:53:22.543 [160/T173] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.543 [160/T168] WARNING: API: Unauthorized
2023-12-27 19:53:22.543 [160/T173] DEBUG_API: API Authentication: FAIL (CSRF token mismatch, received "3HRQdeu6DzBNpWNbVTm3xQ=", expected "4xf2NqgNVVPs/A7puQ4OqA=")
2023-12-27 19:53:22.543 [160/T173] WARNING: API: Unauthorized
2023-12-27 19:53:22.545 [160/T166] DEBUG_API: Received no payload
2023-12-27 19:53:22.545 [160/T166] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.545 [160/T166] DEBUG_API: API Authentication: FAIL (CSRF token mismatch, received "3HRQdeu6DzBNpWNbVTm3xQ=", expected "4xf2NqgNVVPs/A7puQ4OqA=")
2023-12-27 19:53:22.546 [160/T166] WARNING: API: Unauthorized
2023-12-27 19:53:22.680 [160/T170] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.680 [160/T170] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:22.680 [160/T170] DEBUG_API: Rewriting Lua page (settings page): /var/www/html/admin/settings/all ==> /var/www/html/admin/settings-all.lp
2023-12-27 19:53:22.945 [160/T169] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/system ? (null) (Content-Type (null))
2023-12-27 19:53:22.946 [160/T171] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/sensors ? (null) (Content-Type (null))
2023-12-27 19:53:22.946 [160/T169] DEBUG_API: Received no payload
2023-12-27 19:53:22.946 [160/T171] DEBUG_API: Received no payload
2023-12-27 19:53:22.946 [160/T167] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/version ? (null) (Content-Type (null))
2023-12-27 19:53:22.946 [160/T169] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.946 [160/T172] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:53:22.946 [160/T171] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.946 [160/T167] DEBUG_API: Received no payload
2023-12-27 19:53:22.946 [160/T169] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:22.946 [160/T172] DEBUG_API: Received no payload
2023-12-27 19:53:22.946 [160/T171] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:22.946 [160/T167] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.946 [160/T169] DEBUG_API: Processing GET /api/info/system in /api/info/system
2023-12-27 19:53:22.946 [160/T172] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.946 [160/T171] DEBUG_API: Processing GET /api/info/sensors in /api/info/sensors
2023-12-27 19:53:22.946 [160/T167] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:22.946 [160/T172] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:22.946 [160/T167] DEBUG_API: Processing GET /api/info/version in /api/info/version
2023-12-27 19:53:22.946 [160/T172] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:53:22.947 [160/T167] DEBUG_API: Done
2023-12-27 19:53:22.947 [160/T169] DEBUG_API: Done
2023-12-27 19:53:22.947 [160/T172] DEBUG_API: Done
2023-12-27 19:53:22.947 [160/T171] DEBUG_API: Done
2023-12-27 19:53:22.948 [160/T166] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/config ? detailed=true (Content-Type (null))
2023-12-27 19:53:22.948 [160/T168] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/ftl ? (null) (Content-Type (null))
2023-12-27 19:53:22.948 [160/T166] DEBUG_API: Received no payload
2023-12-27 19:53:22.948 [160/T168] DEBUG_API: Received no payload
2023-12-27 19:53:22.948 [160/T166] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.948 [160/T168] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:22.948 [160/T166] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:22.948 [160/T168] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:22.948 [160/T166] DEBUG_API: Processing GET /api/config in /api/config
2023-12-27 19:53:22.948 [160/T168] DEBUG_API: Processing GET /api/info/ftl in /api/info/ftl
2023-12-27 19:53:22.949 [160/T168] DEBUG_API: Done
2023-12-27 19:53:22.953 [160/T166] DEBUG_API: Done
2023-12-27 19:53:23.068 [160/T173] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/messages/count ? (null) (Content-Type (null))
2023-12-27 19:53:23.069 [160/T173] DEBUG_API: Received no payload
2023-12-27 19:53:23.069 [160/T173] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:23.069 [160/T173] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:23, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:23.069 [160/T173] DEBUG_API: Processing GET /api/info/messages/count in /api/info/messages/count
2023-12-27 19:53:23.071 [160/T173] DEBUG_API: Done
2023-12-27 19:53:33.094 [160/T170] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:53:33.094 [160/T170] DEBUG_API: Received no payload
2023-12-27 19:53:33.094 [160/T170] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:33.094 [160/T170] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:33, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:33.094 [160/T170] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:53:33.095 [160/T170] DEBUG_API: Done
2023-12-27 19:53:43.094 [160/T171] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/system ? (null) (Content-Type (null))
2023-12-27 19:53:43.095 [160/T171] DEBUG_API: Received no payload
2023-12-27 19:53:43.095 [160/T169] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/sensors ? (null) (Content-Type (null))
2023-12-27 19:53:43.095 [160/T171] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:43.095 [160/T169] DEBUG_API: Received no payload
2023-12-27 19:53:43.095 [160/T171] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:43, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:43.095 [160/T169] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:43.095 [160/T171] DEBUG_API: Processing GET /api/info/system in /api/info/system
2023-12-27 19:53:43.095 [160/T169] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:43, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:43.095 [160/T169] DEBUG_API: Processing GET /api/info/sensors in /api/info/sensors
2023-12-27 19:53:43.096 [160/T171] DEBUG_API: Done
2023-12-27 19:53:43.096 [160/T169] DEBUG_API: Done
2023-12-27 19:53:43.235 [160/T167] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:53:43.235 [160/T167] DEBUG_API: Received no payload
2023-12-27 19:53:43.235 [160/T167] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:43.235 [160/T167] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:43, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:43.235 [160/T167] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:53:43.236 [160/T167] DEBUG_API: Done
2023-12-27 19:53:53.384 [160/T172] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:53:53.384 [160/T172] DEBUG_API: Received no payload
2023-12-27 19:53:53.385 [160/T172] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:53:53.385 [160/T172] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:53:53, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:53:53.385 [160/T172] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:53:53.385 [160/T172] DEBUG_API: Done
2023-12-27 19:54:03.237 [160/T166] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/sensors ? (null) (Content-Type (null))
2023-12-27 19:54:03.237 [160/T166] DEBUG_API: Received no payload
2023-12-27 19:54:03.237 [160/T166] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:03.237 [160/T166] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:03, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:03.237 [160/T166] DEBUG_API: Processing GET /api/info/sensors in /api/info/sensors
2023-12-27 19:54:03.238 [160/T168] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/system ? (null) (Content-Type (null))
2023-12-27 19:54:03.238 [160/T168] DEBUG_API: Received no payload
2023-12-27 19:54:03.238 [160/T168] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:03.238 [160/T168] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:03, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:03.238 [160/T166] DEBUG_API: Done
2023-12-27 19:54:03.238 [160/T168] DEBUG_API: Processing GET /api/info/system in /api/info/system
2023-12-27 19:54:03.239 [160/T168] DEBUG_API: Done
2023-12-27 19:54:03.518 [160/T173] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:54:03.518 [160/T173] DEBUG_API: Received no payload
2023-12-27 19:54:03.518 [160/T173] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:03.518 [160/T173] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:03, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:03.518 [160/T173] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:54:03.519 [160/T173] DEBUG_API: Done
2023-12-27 19:54:13.679 [160/T170] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:54:13.680 [160/T170] DEBUG_API: Received no payload
2023-12-27 19:54:13.680 [160/T170] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:13.680 [160/T170] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:13, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:13.680 [160/T170] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:54:13.681 [160/T170] DEBUG_API: Done
2023-12-27 19:54:22.944 [160/T171] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/messages/count ? (null) (Content-Type (null))
2023-12-27 19:54:22.944 [160/T171] DEBUG_API: Received no payload
2023-12-27 19:54:22.945 [160/T171] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:22.945 [160/T171] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:22, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:22.945 [160/T171] DEBUG_API: Processing GET /api/info/messages/count in /api/info/messages/count
2023-12-27 19:54:22.948 [160/T171] DEBUG_API: Done
2023-12-27 19:54:23.376 [160/T169] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/sensors ? (null) (Content-Type (null))
2023-12-27 19:54:23.376 [160/T169] DEBUG_API: Received no payload
2023-12-27 19:54:23.377 [160/T167] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/system ? (null) (Content-Type (null))
2023-12-27 19:54:23.377 [160/T169] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:23.377 [160/T167] DEBUG_API: Received no payload
2023-12-27 19:54:23.377 [160/T169] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:23, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:23.377 [160/T167] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:23.377 [160/T169] DEBUG_API: Processing GET /api/info/sensors in /api/info/sensors
2023-12-27 19:54:23.377 [160/T167] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:23, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:23.377 [160/T167] DEBUG_API: Processing GET /api/info/system in /api/info/system
2023-12-27 19:54:23.378 [160/T167] DEBUG_API: Done
2023-12-27 19:54:23.378 [160/T169] DEBUG_API: Done
2023-12-27 19:54:23.830 [160/T172] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:54:23.830 [160/T172] DEBUG_API: Received no payload
2023-12-27 19:54:23.831 [160/T172] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:23.831 [160/T172] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:23, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:23.831 [160/T172] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:54:23.831 [160/T172] DEBUG_API: Done
2023-12-27 19:54:33.964 [160/T166] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:54:33.964 [160/T166] DEBUG_API: Received no payload
2023-12-27 19:54:33.964 [160/T166] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:33.964 [160/T166] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:33, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:33.965 [160/T166] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:54:33.965 [160/T166] DEBUG_API: Done
2023-12-27 19:54:43.516 [160/T173] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/system ? (null) (Content-Type (null))
2023-12-27 19:54:43.516 [160/T168] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/sensors ? (null) (Content-Type (null))
2023-12-27 19:54:43.516 [160/T173] DEBUG_API: Received no payload
2023-12-27 19:54:43.516 [160/T168] DEBUG_API: Received no payload
2023-12-27 19:54:43.516 [160/T173] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:43.516 [160/T168] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:43.516 [160/T173] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:43, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:43.516 [160/T168] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:43, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:43.516 [160/T173] DEBUG_API: Processing GET /api/info/system in /api/info/system
2023-12-27 19:54:43.516 [160/T168] DEBUG_API: Processing GET /api/info/sensors in /api/info/sensors
2023-12-27 19:54:43.517 [160/T173] DEBUG_API: Done
2023-12-27 19:54:43.517 [160/T168] DEBUG_API: Done
2023-12-27 19:54:44.109 [160/T170] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:54:44.109 [160/T170] DEBUG_API: Received no payload
2023-12-27 19:54:44.109 [160/T170] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:44.110 [160/T170] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:44, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:44.110 [160/T170] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:54:44.110 [160/T170] DEBUG_API: Done
2023-12-27 19:54:54.245 [160/T171] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:54:54.245 [160/T171] DEBUG_API: Received no payload
2023-12-27 19:54:54.245 [160/T171] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:54:54.245 [160/T171] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:54:54, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:54:54.245 [160/T171] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:54:54.246 [160/T171] DEBUG_API: Done
2023-12-27 19:55:03.707 [160/T167] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/sensors ? (null) (Content-Type (null))
2023-12-27 19:55:03.707 [160/T167] DEBUG_API: Received no payload
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/info/system ? (null) (Content-Type (null))
2023-12-27 19:55:03.707 [160/T167] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Received no payload
2023-12-27 19:55:03.707 [160/T167] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:55:03, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:55:03.707 [160/T167] DEBUG_API: Processing GET /api/info/sensors in /api/info/sensors
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:55:03, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:55:03.707 [160/T169] DEBUG_API: Processing GET /api/info/system in /api/info/system
2023-12-27 19:55:03.708 [160/T167] DEBUG_API: Done
2023-12-27 19:55:03.708 [160/T169] DEBUG_API: Done
2023-12-27 19:55:04.388 [160/T172] DEBUG_API: Requested API URI: 192.168.0.1 -> GET /api/dns/blocking ? (null) (Content-Type (null))
2023-12-27 19:55:04.388 [160/T172] DEBUG_API: Received no payload
2023-12-27 19:55:04.388 [160/T172] DEBUG_API: Read sid="*****" from cookie
2023-12-27 19:55:04.389 [160/T172] DEBUG_API: Recognized known user: user_id 3, valid_until: 2024-01-03 19:55:04, remote_addr 192.168.0.1 (192.168.0.1 at login)
2023-12-27 19:55:04.389 [160/T172] DEBUG_API: Processing GET /api/dns/blocking in /api/dns/blocking
2023-12-27 19:55:04.389 [160/T172] DEBUG_API: Done
from ftl.
akordowski
commented on August 16, 2024
@DL6ER I tested it multiple times and as I can say the API calls are working as expected. As the only issue is that the GUI is not working properly, when the DNS blocking is disabled via the API, I would close this issue and open a new one. What do you think?
from ftl.
akordowski
commented on August 16, 2024
That sounds great, thank you! Than I will close this issue.
from ftl.
DL6ER
commented on August 16, 2024
The timer fix has been merged into development-v6
from ftl.
Related Issues (20)
- debug.api help text needs another description HOT 1
- FTL Crash HOT 4
- Unable to build FTL from source HOT 9
- app password not working in v6 HOT 7
- [Pi-hole V6] Ftl crash because of database? HOT 10
- [Beta V6] FTL-Checksum error? HOT 4
- Compilation failure with GCC 14 HOT 7
- dns.hosts(0): invalid hostname HOT 4
- v6 Seg fault crash on first startup macOS M2 HOT 14
- Pihole-FTL v6 crash when ipv6 disabled and ipv6 dns given. HOT 2
- crash on internet outage HOT 6
- v6: documentation on PUT /clients/ is not complete HOT 8
- DHCP server is configured with incorrect netmask HOT 8
- Pihole is not installing update HOT 6
- Overzealous inline opitimizations? HOT 7
- FTL crashes when activating DHCP server HOT 6
- dev: webserver doesn't properly detect mbedtls dependency HOT 6
- PTR requests not being generated for local clients HOT 26
- Client ipv6 hostnames is not resolving and not being stored in FTL database HOT 5
- Obsolete MAC Vendor DB Script HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ftl.