mirror of
https://github.com/chr0nzz/traefik-manager.git
synced 2026-05-09 05:35:22 +02:00
[GH-ISSUE #7] Error when saving new file #5
Labels
No labels
bug
bug
bug
feature request
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/traefik-manager#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wolfnacht44 on GitHub (Apr 5, 2026).
Original GitHub issue: https://github.com/chr0nzz/traefik-manager/issues/7
Originally assigned to: @chr0nzz on GitHub.
Think I hit a bug
Linux Native: v0.10.0
OS: Ubuntu 24.04.4LTS
app kicking back an error when trying to save a middleware or route as a "new file".
Error one, it defaults to the first file it finds, then when removing and resaving as a NEW file
the action errors out, and journalctl reports _is_safe_path is not defined.
gunicorn[3339]: 2026-04-05 17:18:31,722 [ERROR] [traefik-manager] Error saving configuration
gunicorn[3339]: Traceback (most recent call last):
gunicorn[3339]: File "/opt/traefik-manager/app.py", line 1816, in save_entry
gunicorn[3339]: target_path = _resolve_config_path(config_file_raw) or CONFIG_PATH
gunicorn[3339]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gunicorn[3339]: File "/opt/traefik-manager/app.py", line 152, in _resolve_config_path
gunicorn[3339]: if _is_safe_path(candidate):
gunicorn[3339]: ^^^^^^^^^^^^^
gunicorn[3339]: NameError: name '_is_safe_path' is not defined
@chr0nzz commented on GitHub (Apr 5, 2026):
found the issue, give me a minute and ill push an update
@wolfnacht44 commented on GitHub (Apr 5, 2026):
Yes, Line 152 in app.py, replaced _is_safe_path with _safe_file_path fixed it locally.
@chr0nzz commented on GitHub (Apr 5, 2026):
please update to v0.10.1
and let me know if it solved the issue
@wolfnacht44 commented on GitHub (Apr 5, 2026):
Update resolved the issue. I got another coming at you shortly.