"could not start or reach the proximamp agent"

One proximamp process per user holds the sign-in and the tunnels on a computer, the agent, and the command could not start it or reach it. Run the command again: if there is no agent, a new one starts by itself.

The error comes as one of these texts: "could not start or reach the proximamp agent: …" with the cause at the end, "the proximamp agent did not answer in time", or "the proximamp agent stopped before it answered". The exit code is 6.

What to do

Run the command again.
If the error repeats, stop the proximamp commands that are running (their tunnels close): Ctrl+C in their windows, or, with no window, end your user's proximamp processes. On Linux:
```
pkill -x -u "$(id -u)" proximamp
```
On Windows, end proximamp.exe with your user name in Task Manager; proximamp-sidecar.exe is the app, leave it. Then run the command again: a stuck agent keeps a new one from starting.
On Linux, check that the program's folders are yours (or the proximamp folders in $XDG_CONFIG_HOME and $XDG_STATE_HOME):
```
ls -ld ~/.config/proximamp ~/.local/state/proximamp
```
You should be the owner. In a Docker container with a host folder instead of the volume (./data on the Docker page), the folder's owner must be user 10001: in the folder with compose.yml, give it to that user and restart the container:
```
sudo chown -R 10001:10001 data
docker compose restart proximamp
```
If proximamp warns that a folder "may be changed by other users of this computer", restrict it as the warning says:
```
chmod 700 <folder>
```
If it says "the agent's socket path … is too long for this system", set the socket folder /run/user/<your id> before the command if it exists, and otherwise a shorter XDG_STATE_HOME, as the program advises:
```
ls -ld /run/user/$(id -u)             # does the folder exist
export XDG_RUNTIME_DIR=/run/user/$(id -u)
```
On Windows the program says "… is too long for Windows": in the same window, set a short folder inside your user folder, not at the root of a drive, and run the command again. In PowerShell:
```
$env:LOCALAPPDATA="$env:USERPROFILE\px"
```
Set it in every new window: it works only in the one where you set it. The sign-in stays, and the tunnels' addresses may change.

In cmd:
```
set LOCALAPPDATA=%USERPROFILE%\px
```

Run the command with a log in a log.txt file: it shows where the agent stopped.

PROXIMAMP_LOG=debug proximamp <command> 2> log.txt

$env:PROXIMAMP_LOG='debug'
proximamp <command> 2> log.txt
Remove-Item Env:PROXIMAMP_LOG

If that didn't help

Click "Ask a question" at the bottom of the page and include the exact error text, the output of proximamp version and the log.txt file from step 6.

What to do​

If that didn't help​

What to do

If that didn't help