When you ask for help, people need to see your logs. This page shows you how to make one log file that Deployrr cleans up for you, and how to check it before you share it.
Before you start
Section titled “Before you start”- Finish Prerequisites first. Without your username and Domain 1, Deployrr can’t replace them, or your public IP, in the log.
- Your server has internet access. Deployrr looks up your public IP online. If the first lookup service shows a Cloudflare challenge, you see “Trying alternate method” and it tries a second one.
- You have run Deployrr at least once, so there are logs to collect.
-
Start Deployrr from the folder where you want the log saved.
Deployrr saves the log in the folder you are in when you run
deployrr. -
From the main menu, select Settings.
-
Select Logs (“Generate Sanitized Deployrr Log”). The screen is titled Sanitized Log for Troubleshooting.
-
Read the warnings in step 1/4, then press
Yto continue. Any other key takes you back. -
Wait for the screen to finish. It collects Deployrr’s own log and, if you have one, the Traefik log. Both go into one file.
-
Note the path after
Location:. The screen ends with “Sanitized log ready for sharing”.
Each run makes a new file named deployrr-log-sanitized-YYYYMMDD_HHMMSS.log.
To see where this option sits in the menu, watch Deployrr 5 walkthrough: Generate a sanitized log in Settings at 15:04. It shows Deployrr v5, so menus and steps differ in v6.
If you see [ERROR] lines
Section titled “If you see [ERROR] lines”The screen can end with “Sanitized log ready for sharing” even when a step in 3/4 failed. Treat any [ERROR] line as a step that did not run:
- If the path after
Location:does not exist, there were no logs to collect yet. Reproduce your problem, then run Logs again. - If the file exists, check it by hand as shown below. Something was not replaced.
What gets replaced
Section titled “What gets replaced”| In the log | Becomes |
|---|---|
| Domain 1 | example.com |
| Your Linux username | USERNAME |
| Your public IP, when it matches the IP Domain 1 points to | XXX.XXX.XXX.XXX |
| Your public IP, when it differs (for example Cloudflare proxy is on) | CIP.CIP.CIP.CIP |
| The IP Domain 1 points to, when it differs from your public IP | RIP.RIP.RIP.RIP |
Only IPv4 addresses are replaced. IPv6 addresses stay as they are.
Every match is replaced, even inside other words. For example, other words that contain your username change too. This is cosmetic.
If your public IP is not replaced
Section titled “If your public IP is not replaced”If Domain 1 is not set (Local mode) or does not resolve, Deployrr does not replace your public IP. Step 3/4 then shows “Replacing resolved IP address (EMPTY → EMPTY.EMPTY.EMPTY.EMPTY)” followed by an [ERROR] line. Open the file and remove your public IP by hand.
Check the log before you share it
Section titled “Check the log before you share it”The file is owned by root. To edit or delete it, use sudo. If you can’t open it as your normal user, use sudo for that too.
-
Find your public IP and your server’s hostname:
Terminal window curl -4 ifconfig.mehostname -
Search the log for your private details. Replace
YOUR_LOG_FILEwith the path you noted. ReplaceYOUR_DOMAIN,YOUR_PUBLIC_IPandYOUR_HOSTNAMEwith your own values. The@finds email addresses.Terminal window grep -n -i -E "YOUR_DOMAIN|YOUR_PUBLIC_IP|YOUR_HOSTNAME|@" YOUR_LOG_FILE -
Search for other secrets:
Terminal window grep -n -i -E "token|password|secret|api[_-]?key" YOUR_LOG_FILE -
Check for your public IPv6 address. Deployrr doesn’t replace IPv6 addresses. This prints your public IPv6, or an error if your server has none:
Terminal window curl -6 ifconfig.meIf it prints an address, search the log for its first three groups (the parts between the colons), for example
2001:db8:1234:Terminal window grep -n -i "YOUR_IPV6_START" YOUR_LOG_FILE -
Also look for Domain 2 and any other domain you use.
-
If you find anything private, open the file and edit it:
Terminal window sudo nano YOUR_LOG_FILETo search inside nano, press
Ctrl+W. To save and exit, pressCtrl+X, thenY, thenEnter. -
Search again until nothing private is left.
Share the log
Section titled “Share the log”-
Attach the file to your message on Discord. Do not paste it as text. See Get help on Discord.
-
When you are done, delete the file if you want:
Terminal window sudo rm YOUR_LOG_FILE
Check it worked
Section titled “Check it worked”- The screen showed “Sanitized log ready for sharing”.
- The file exists at the path after
Location:. - Your domain shows as
example.comand your username asUSERNAME. - Searching for your public IP, your hostname and the start of your IPv6 address finds nothing.

