English Troubleshooting

Troubleshooting

First diagnostic path

1. Check MANUAL ACTIONS in the Control Center.
2. Check Home RAM, operating phase, and executable-task count.
3. Run the self-test:

run tools/self-test.js

4. If files are missing or outdated:

run git-pull.js

On a Home server below 16 GiB, use:

run git-pull-lite.js
run autoDoIt.js

“Not enough RAM”

This is often not an error. The scheduler starts a module only when its current BitNode RAM price fits beside the scheduler, dashboard, and running tasks.

• Below 32 GiB, only bootstrap tasks are selected.
• At 32 GiB, the lightweight phase begins.
• Large Singularity modules can be much more expensive with SF4 level 1 because of the external RAM multiplier.
• If Home RAM cannot yet be purchased automatically, raise it manually once to the level recommended in the Control Center.

Hacking workers on rooted and purchased servers continue earning meanwhile.

No cloud servers are purchased

Cloud servers have a dedicated budget. Small servers are valid early purchases; when even the minimum size is too expensive, the 1% allocations are banked. At the server limit, the weakest server is later upgraded or safely replaced.

Check:

• Is enough money available above the protected reserve?
• Is tasks/manage-purchased-servers.js executable in the current phase?
• Does recent activity say that cloud servers are waiting for upgrade budget?

The network is not fully rooted

Root access depends on Hacking level and port programs. The network manager names the exact missing program. The usual sequence is:

• BruteSSH
• FTPCrack
• relaySMTP
• HTTPWorm
• SQLInject

More rooted servers provide more worker RAM, but they are not all good money targets. A beginner run attacking foodnstuff for a long time may be correct.

The dashboard does not appear

• Automatic startup begins at 32 GiB Home RAM by default.
• Check whether --no-ui was used.
• Start it manually:

run ui/dashboard.js

• Leave auto-fit enabled for small windows.
• If the language is wrong, click DE/EN or restart with --lang de or --lang en.

The auto-updater appears idle

The default check interval is 15 minutes. The Control Center displays:

up to date VERSION (next check: TIMER)

Nothing restarts when versions match. Use run git-pull.js for an immediate manual update. Network failures must not overwrite the working installation.

Casino is invisible or keeps reloading

Saving after a win and reloading after a loss is intended. During the Casino opening phase:

• keep Bitburner in the foreground
• expand Overview
• do not operate another visible page

After reaching the target, the module opens Stats. Follow any yellow Casino notice once if a required UI control is hidden.

Darknet stops progressing

Darknet servers can have very little RAM. The manager first starts a light seeder and promotes it to the full crawler when a suitable neighbor has enough RAM.

Every Darknet launcher opens local .cache stashes first. A successfully collected reward appears in the Control Center as Darknet cache opened.

Check:

• Is darknetEnabled enabled?
• Are Darkweb/Darknet reachable and authenticated?
• Does the Control Center report a launched seeder?
• Was the current version downloaded completely?

Repair missing workers after an update with run git-pull.js.

Jobs/factions are not controlled automatically

Without Source-File 4, Singularity is unavailable and autoDoIt can only provide concrete recommendations. With SF4, the relevant module also needs enough free RAM.

Incompatible city factions are selected according to preferredCityFactions, preventing automatic joining from blocking a more important route.

Report a bug

Include:

• Bitburner version
• autoDoIt version from the Control Center
• current BitNode and Source-File state
• Home RAM and operating phase
• exact yellow/red message
• steps leading to the problem

Use the repository's Issues or the project discussion. Do not upload personal save files publicly.