I run the latest versions 6.0 beta version in a docker container.
I have a problem when trying to edit or delete one of the groups. The group is called Samsung A54.
When trying to edit the group name i get the following error: Spaces, newlines and tabs are not allowed in domains and URLs
Samsung A54
When i try to delete the group i get this error: Could not remove entries from table
FOREIGN KEY constraint failed
Editing of deleting other groups gives no error.
Could you help me out?
Thanks in advance
Relevant versions:
Core vDev (development, 6b423f53)
FTL vDev (development, c71c5273)
Web interface vDev (development, 47e977a2)
First I have one question to understand how this happened:
How did you create a group name with spaces?
I tried to create a group called "Group with spaces" via web interface, but the attempt resulted in 3 different groups: Group
, with
and spaces
.
Probably, not sure.
I just now tried with "test group" which indeed resulted in 2 groups called test and group.
But i was able to edit/delete both
Ok.
I was able to create a group without spaces and then edit the name to include spaces, but I have no issues editing or deleting this groups. Apparently you have a different and unexpected issue.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
I entered pihole -d command in terminal, get a long text but cant find token url
get a long text but cant find token url
When the "long text" is finished, did you see this question?
********************************************
[✓] ** FINISHED DEBUGGING! **
* The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[?] Would you like to upload the log? [y/N]
Please answer Y and wait for the token.
No, i get this.
[✓] ** FINISHED DEBUGGING! **
The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
* Log will NOT be uploaded to tricorder.
* A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log
That message indicates that you didn't reply with Y when asked whether you would like to upload the log.
I never got that question.
is this because i run pihole in a docker container and not natively in raspberry pi os?
I did however copy the log output i got on my screen.
How are you running pihole -d
? If you do not use an interactive session then you will not get the option. You can do a pihole -d -a
for an automated debug run with uploading enabled.
I have the same error if i delete a group (groupname without spaces).
My system:
Docker Tag nightly
Core vDev (development, 03932e8c)
FTL vDev (development, 84780798)
Web interface vDev (development, 9f9c26c5)
I create a debug log
Token: https://tricorder.pi-hole.net/tqyCzPWg/
Because i run pihole in docker i use the command docker exec pihole pihole -d
The run the command I showed above or add -it
to your docker exec for an interactive terminal.
docker exec -it pihole pihole -d
or docker exec pihole pihole -d -a
1 Like
I still have this problem.
Seems to happen when i add a group and later edit the group name inserting a space.
After that i get the errors.
We are actually working on this issue.
DL6ER
December 24, 2024, 1:47am
17
Sorry for this having been overseen for so long. At the very least, I was just able to follow your instructions (create group a
, then edit spaces into the name like Galaxy A53
and then try to e.g., disable the group) and can confirm this behavior:
This is a small bug in the API code processing PUT /api/groups
and should be fixed by
pi-hole:development
← pi-hole:fix/put_groups
opened 01:46AM - 24 Dec 24 UTC
# What does this implement/fix?
Fixes a bug reported on Discourse:
![image](… https://github.com/user-attachments/assets/5b763d5b-fa50-4836-b57a-d885d1166f6a)
---
**Related issue or feature (if applicable):** N/A
**Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A
---
**By submitting this pull request, I confirm the following:**
1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against.
2. I have commented my proposed changes within the code.
3. I am willing to help maintain this change if there are issues with it later.
4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
## Checklist:
- [x] The code change is tested and works locally.
- [x] I based my code and PRs against the repositories `developmental` branch.
- [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions
- [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship
- [x] I have read the above and my PR is ready for review.
Fixing being able to add groups with spaces in the very first place (enclosed in quotes) will be done by
pi-hole:development
← pi-hole:new/group_assign
opened 11:40AM - 23 Dec 24 UTC
# What does this implement/fix?
See the related Discourse Feature request for… screenshots: https://discourse.pi-hole.net/t/add-group-management-dropdown-to-add-a-new-domain-or-regex-filter/74696
---
**Related issue or feature (if applicable):** https://discourse.pi-hole.net/t/add-group-management-dropdown-to-add-a-new-domain-or-regex-filter/74696
**Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A
---
**By submitting this pull request, I confirm the following:**
1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against.
2. I have commented my proposed changes within the code.
3. I am willing to help maintain this change if there are issues with it later.
4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
## Checklist:
- [x] The code change is tested and works locally.
- [x] I based my code and PRs against the repositories `developmental` branch.
- [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions
- [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship
- [x] I have read the above and my PR is ready for review.
DL6ER
December 24, 2024, 5:52am
18
The first of the two fixes has been merged into development
1 Like
Fix works, i love you guys
1 Like