[Bug]: Outline Manager cannot create new valid keys

[pavelgivoy]

Application

Outline Manager

Describe the bug

The Outline Manager cannot create new valid keys to use VPN server. The server is running and alive.

Steps to reproduce

1. Open the Outline Manager
2. Choose my server
3. Create a new key and get a response that the key cannot be created
   
4. Close the Outline Manager
5. Open the Outline Manager again, and I see that the key is created
   
6. Open the Outline client
7. Insert the created key here and get the response that the key is invalid
   

What did you expect to happen?

I expect that the valid key is created and can be used for new connections

What actually happened?

All created keys are invalid

Outline Version

1.15.2 (Manager); 1.12.0 (Client Windows); 1.13.0 and 1.14.0 (Client iOS)

What operation system are you using?

iOS, Windows

Operating System Version

Windows 10 22H2 (Manager and Client)
iOS 18.0.1 (Client)
iOS 17.7.6 (Client)

Screenshots and Videos

All screenshots are given above at reproducing steps unit

P.S. I already have three keys for the current server, that are successfully working. This problem is actual for the newer keys.

[sbruens]

It's hard to tell whether this is a Manager application issue or a server API issue. Are you able to use the API directly to try and create a key and see the response? Here are instructions on how to use the API: https://github.com/Jigsaw-Code/outline-server/tree/master/src/shadowbox#access-keys-management-api

[pavelgivoy]

I created the key directly via API. The created key is shown when I use API command to list all keys. Get command also shows that key. When I put it into Outline Client, it says that the key is invalid

[sbruens]

Can you validate the format of the key you created? For example, I'd expect it to look something like this: ss://[email protected]:17178. Make sure the IP (the 1.2.3.4 example in the URL above) is set.

You can also inspect the docker logs from around the time you created the key, or create a new key and check the logs to see if the same error happens. That will help us understand what error is causing this. You can run docker logs shadowbox from inside the server to get the logs.

My guess of what's happening is that there is a problem happening here, where the key is getting created but not cleaned up in the error case. We could show a better error message in the Manager. Although I'm surprised the API doesn't error on creating a new key either. Seeing the docker logs will help pinpoint the problem.

[pavelgivoy]

The key format satisfies your example. The IP address is set.

According to logs, the last entry in them is:
ts=2024-11-14T04:00:53.021Z caller=scrape.go:1277 level=error component="scrape manager" scrape_pool=outline-server-main target=http://127.0.0.1:9091/metrics msg="Scrape commit failed" err="write to WAL: log samples: write /opt/outline/persisted-state/prometheus/data/wal/00000009: no space left on device"

I don't have newer entries, even if I'm trying to create new keys, and I cannot know what the server does with created keys. In my suggestion, the server doesn't create them because of lack of disk space. But it's better for you to make your own analysis of my issue.

[sbruens]

Yes, it seems likely the lack of disk space is causing issues. It's probably unable to update the outline-ss-server config with the new key because that requires writing to disk. Resolving the disk space issue first will help you debug further, but that may resolve it completely.