[GH-ISSUE #9] problem Error 1033 #9

New issue

Open

opened 2026-02-27 21:00:47 +03:00 by kerem · 2 comments

kerem commented 2026-02-27 21:00:47 +03:00

Owner

Copy link

Originally created by @elviosilva on GitHub (Aug 16, 2025).
Original GitHub issue: https://github.com/sfnemis/proxmox-traefikproxy-cloudflaretunnel/issues/9

wget -O /etc/traefik/dynamic/fileConfig.yml https://github.com/sfnemis/proxmox-traefikproxy-cloudflaretunnel/raw/main/etc/traefik/dynamic/fileConfig.yml
read -p "Enter username: " USER && read -s -p "Enter password: " PASS && echo && HASH=$(htpasswd -nbB "$USER" "$PASS") && sed -i "s|admin:.*|$HASH|" /etc/traefik/dynamic/fileConfig.yml

Hello, on this line, which user and password should I enter?

Those for the Cloudflare account?

Originally created by @elviosilva on GitHub (Aug 16, 2025). Original GitHub issue: https://github.com/sfnemis/proxmox-traefikproxy-cloudflaretunnel/issues/9 wget -O /etc/traefik/dynamic/fileConfig.yml https://github.com/sfnemis/proxmox-traefikproxy-cloudflaretunnel/raw/main/etc/traefik/dynamic/fileConfig.yml read -p "Enter username: " USER && read -s -p "Enter password: " PASS && echo && HASH=$(htpasswd -nbB "$USER" "$PASS") && sed -i "s|admin:.*|$HASH|" /etc/traefik/dynamic/fileConfig.yml Hello, on this line, which user and password should I enter? Those for the Cloudflare account?

kerem commented 2026-02-27 21:00:48 +03:00

Author

Owner

Copy link

@elviosilva commented on GitHub (Aug 16, 2025):

Hello,
After four installations, I still receive an error 1033 when trying to run https://test.example.com.

Can you help me pls?

<!-- gh-comment-id:3193796616 --> @elviosilva commented on GitHub (Aug 16, 2025): Hello, After four installations, I still receive an error 1033 when trying to run https://test.example.com. Can you help me pls?

kerem commented 2026-02-27 21:00:48 +03:00

Author

Owner

Copy link

@bagav1 commented on GitHub (Feb 18, 2026):

The username and password requested there are intended to be used with HTTP Basic Authentication. When accessing the routes defined in Traefik, it will prompt for these credentials (as I understand it).

Regarding error 1033, I encountered the same issue.

The problem occurred after configuring the local configuration file /etc/cloudflared/config.yml. I then checked the Cloudflare tunnel in the dashboard, which caused the tunnel configuration to switch to a remote-managed state. As a result, the DNS configuration defined in the local file was completely ignored.

Solution

1. Delete the existing tunnel (both locally and from the Cloudflare dashboard).
   1. Go to your Cloudflare dashboard and select your domain (e.g. example.com).
   2. Go to the DNS > Records section.
   3. Find the CNAME records that say example.com and *.example.com (or (root) and *).
   4. Delete them.
2. Remove the DNS records previously created in Cloudflare.
3. Recreate the tunnel using the CLI commands below.
4. Avoid interacting with the tunnel configuration from the Cloudflare dashboard afterward.

systemctl stop cloudflared
rm -f /etc/cloudflared/cert.pem
rm -f /etc/cloudflared/*.json
rm -f /root/.cloudflared/*.json
rm -f /root/.cloudflared/cert.pem

cloudflared tunnel login
cloudflared tunnel create traefik

cp /root/.cloudflared/{newTunnelID}.json /etc/cloudflared/credentials.json

cloudflared tunnel route dns {newTunnelID} *.example.com
cloudflared tunnel route dns {newTunnelID} example.com

Important: Replace the tunnel ID in /etc/cloudflared/config.yml with the newly created tunnel ID.

cloudflared service install
systemctl daemon-reload
systemctl start cloudflared

<!-- gh-comment-id:3923589810 --> @bagav1 commented on GitHub (Feb 18, 2026): The username and password requested there are intended to be used with **HTTP Basic Authentication**. When accessing the routes defined in Traefik, it will prompt for these credentials (as I understand it). Regarding error 1033, I encountered the same issue. The problem occurred after configuring the local configuration file `/etc/cloudflared/config.yml`. I then checked the Cloudflare tunnel in the dashboard, which caused the tunnel configuration to switch to a remote-managed state. As a result, the DNS configuration defined in the local file was completely ignored. ### Solution 1. Delete the existing tunnel (both locally and from the Cloudflare dashboard). 1. Go to your [Cloudflare dashboard](https://dash.cloudflare.com) and select your domain (e.g. example.com). 2. Go to the DNS > Records section. 3. Find the CNAME records that say example.com and *.example.com (or (root) and *). 4. Delete them. 3. Remove the DNS records previously created in Cloudflare. 4. Recreate the tunnel using the CLI commands below. 5. Avoid interacting with the tunnel configuration from the Cloudflare dashboard afterward. ```bash systemctl stop cloudflared rm -f /etc/cloudflared/cert.pem rm -f /etc/cloudflared/*.json rm -f /root/.cloudflared/*.json rm -f /root/.cloudflared/cert.pem cloudflared tunnel login cloudflared tunnel create traefik cp /root/.cloudflared/{newTunnelID}.json /etc/cloudflared/credentials.json cloudflared tunnel route dns {newTunnelID} *.example.com cloudflared tunnel route dns {newTunnelID} example.com ``` **Important:** Replace the tunnel ID in `/etc/cloudflared/config.yml` with the newly created tunnel ID. ```bash cloudflared service install systemctl daemon-reload systemctl start cloudflared ```

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

No results found.

Labels

Clear labels   

pull-request

Mirrored from GitHub Pull Request

No labels

pull-request

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxmox-traefikproxy-cloudflaretunnel#9

No description provided.