Guild is back: what to do after the recovery
Service is running · updated 9 October 2026
We had to rebuild the Guild server from scratch. Your agents, projects and conversations are still on your computer. Devices and integrations must be connected again — the order and the exact steps are below.
If something goes wrong, message us on Telegram or at guild@morozov.digital.
What happened
On 8 October, Yandex Cloud zone ru-central1-b, where the Guild server ran, became unavailable. The provider reports a fire following a drone attack on its data centre. Yandex Cloud incident 2092.
The server and its database lived only in that zone, and we had no backup outside it. That was our mistake. The server data could not be recovered: we recreated accounts from e-mail addresses, and everything else has to be set up again.
What we changed
Guild now runs on two servers in different zones with a shared database and automatic failover. Backups are stored separately from the servers.
Your devices
Mac, Windows, Linux, iPhone, Android and the browser
encrypted connection
Yandex Cloud
Application Load Balancer
Single entry point
Checks the servers and sends requests to the one that is working.
Zone ru-central1-a
Compute Cloud
Guild server
Managed Service for PostgreSQL
Database host
Zone ru-central1-d
Compute Cloud
Guild server
Managed Service for PostgreSQL
Database host
One server works and the other takes over automatically: in our test the switch took 38 seconds. The database is shared, and its hosts replicate data between the zones.
database backups
Object Storage
Backups and builds
Encrypted database backups are made every day and kept for 35 days. They are stored separately from the servers.
copy of the builds
Outside Yandex Cloud
Build mirror
The applications and the recovery script can be downloaded even if the cloud is unavailable.
What survived and what must be redone
Still on your computer
- Agents, teams, history, the task board, agent mail
- Projects and their secrets, the wiki, schedules and duties
- Files in your project folders
- Model keys, Claude Code and Codex sign-ins
- Center and Bitrix24 connections
- Private SSH keys
Must be done again
- Sign in to your account
- Activate the computer and the phone with new keys
- Pair the phone with the computer
- Telegram, Yandex Disk, Google, Notion, Images
- GitLab, GitHub, clouds, servers, storage buckets
- Public agent links and browsers
- Skills and roles from the account, notification settings
Do not reinstall Guild
Do not delete the application or agent folders: that will not restore the connection to the server, and you may lose data.
Recovery order
The order matters
The computer first, then the phone. The phone connects with a QR code shown by a computer that is already working. Until the computer is activated, the phone cannot be connected.
Sign in to your account
With a link from the e-mail. There is no password.Activate the computer
With a new key from your account. Steps for Mac, Windows and Linux are below.Update the application
The latest build installs from the application settings.Connect the phone
The phone needs its own key, then a QR code from the computer.Reconnect integrations
Telegram, Yandex Disk, repositories, clouds and servers — again.
1. Sign in to your account
Open your account and enter your e-mail
Open your account. Enter your e-mail on the sign-in page and request a link.Follow the link from the e-mail
The link is valid for 15 minutes and works once.
- There is no password: you always sign in with a link from the e-mail.
- The account does not recognise your address — sign up with the same address and write to us: we will check your account.
2. Activate the computer: Mac
Request an activation key
In your account, open the connection page and request an activation key. The key is valid for one hour and connects one device.Open Guild and look at the screen
Then follow one of the three options.
Option 1 · the screen shows
The activation key field
Enter the key and activate. Done — move on to updating the application.
Option 2 · the screen shows
The Guild server is not responding, and there is no key field
The application remembers the previous activation, which the new server does not have. Remove it with a command in Terminal.
Quit Guild completely
Press Command-Q.Open Terminal
Paste the whole command and press Enter
Do not use sudo.
/bin/bash -c 'set -euo pipefail; file=$(mktemp -t guild-reset); trap "rm -f \"$file\"" EXIT; curl -fsSL --connect-timeout 15 --max-time 60 "https://guild-releases.fra1.cdn.digitaloceanspaces.com/support/reset-mac-activation-20261009-v1-af052ec3c877.sh" -o "$file"; printf "%s %s\n" "af052ec3c877ca2dd0e711e049c0df3066550d2538a7d6e6e38cd1a8f0423a5a" "$file" | /usr/bin/shasum -a 256 -c -; /bin/bash "$file"'Read the explanation on screen and type YES
Open Guild and enter the new key from your account
What the command does
- Downloads our script, verifies its checksum and runs it only if the checksum matches.
- Removes the previous device certificate and three licence status flags.
- Does not touch agents, history, projects or the device key.
- Never asks for or prints passwords.
Read the script before running it
If the command did not work
- It says Guild is still open — quit the application with Command-Q and run it again.
- The script does not download — turn on a VPN or write to us.
Option 3 · Guild is open and working
Settings say there is no connection and Guild is reconnecting
Guild has not been quit since the outage: agents work, but there is no connection to the server or the phone. You do not need Terminal — the previous activation is removed in the settings.
Wait until the agents finish their work
When the activation is removed, Guild stops all agents.Open Settings → Connection, the licence section
Remove the activation
Guild will show the activation key screen right away.Enter the new key and activate
Restart the connection
In Settings → Connection, turn phone access off and on again. A running application does not switch to the new activation by itself.
The notice about the lost connection should disappear within a minute. If it stays, quit Guild with ⌘Q and open it again.
2. Activate the computer: Windows
Request an activation key
In your account, open the connection page, choose Windows and request an activation key.Open Guild and look at the screen
Then follow your option.
Option 1 · the screen shows
This computer was revoked in the account
Choose to enter a new key and paste it.
Option 2 · the screen shows
Guild cannot start in WSL
Open the setup wizard
On the activation key step, choose to enter a new key
Paste the key and activate
Option 3 · fallback
The wizard does not open
Close Guild
Run the reset command in PowerShell
wsl -d guild -- bash -lc "guild-host reset-identity"Open Guild and enter the key
What the command does
- Removes the previous device key and certificate and the saved server address.
- Agents, history and Claude Code and Codex sign-ins stay.
- You do not need to remove or reinstall the WSL environment.
If Guild still does not start
Check the connection to the server: the commands for Windows are in the section on checking the connection below. They change nothing.
2. Activate the computer: Linux
Request an activation key
In your account, on the connection page.Remove the previous activation and enter the new key
These are two commands for
guild-host. Replace XXXX-XXXX-XXXX with your key.guild-host reset-identity guild-host activate --code XXXX-XXXX-XXXX
Agent data stays in place.
3. Update the application
- Mac
- Settings → General → Update → check for updates.
- Windows
- Settings → System → Updates → check now.
- iPhone
- Update Guild in TestFlight. The beta link is in your account, on the iPhone tab.
- Android
- Download the latest APK in your account, on the Android tab, and install it over the previous one.
The latest builds are also in your account if you need to install again.
4. Connect the phone
The phone needs its own key
The computer key will not work. By this point the computer must be activated and Guild must be open on it.
Open Guild on the phone
On the screen saying the device was revoked or has no access, choose to connect again.Request a key for the phone
In your account, open the connection page, choose the phone tab and request an activation key.Enter the key on the phone
Type the key or scan the code shown next to it.Show the QR code on the computer
- Mac
- Settings → Connection, turn on phone access, then show the pairing QR.
- Windows
- Settings → Connection → Phones → show the QR code.
Scan the QR code with the phone
Choose to scan the QR and point the camera at the code.Confirm the phone on the computer
Choose to allow it.
If the phone screen says
Access could not be verified, or the computer is not responding
Retry the check
If that does not help, reset the activation
Repeat the steps above with a new key
5. Reconnect integrations
Connections from the integrations section were stored on the server and did not survive. Reconnect the ones you use.
Find your tokens and keys first
After activation the application syncs with your account. The new account has no connections yet, so the application will remove the saved copies of repository tokens, cloud keys, server passwords and storage keys from the computer.
The repositories, clouds and servers themselves are not affected. To connect them again you will need the original tokens and keys. If you no longer have them, issue new ones with the provider.
What to reconnect
- Telegram
- Your bot and recipients — in the integrations section. Personal Telegram is linked in Guild settings.
- Drives and documents
- Yandex Disk, Google, Notion, Images.
- Repositories
- GitLab and GitHub.
- Infrastructure
- Clouds, servers, storage buckets.
- Links and browsers
- Create public agent links again. Link browsers for Guild in the browser once more.
- Skills and roles
- Those installed from the account must be installed there again.
What you do not need to reconnect
- Private SSH keys, project secrets and model keys stayed on the computer: they were never sent to the server.
- Center and Bitrix24 connections are in place too.
Checking the connection to the server
If Guild still says the server is not responding after activation, check the connection. The commands below only show settings and the server address and change nothing.
Terminal
Mac
defaults read com.continental.guild service.relayHost
nslookup connect.app.continental-c.com- The first command shows the saved server address. A reply saying it does not exist means the Mac is not activated yet.
- The second must end with an Address line holding the server address. A reply that the name cannot be found or that the request timed out means the network is in the way.
PowerShell
Windows
nslookup connect.app.continental-c.com
wsl -d guild -- bash -lc "guild-host doctor"- The first command must end with an Address line holding the server address. The words “Non-authoritative answer” are a normal nslookup note, not an error.
- The second prints a report in Russian, line by line. The line that mentions connect.app.continental-c.com and TCP :443 shows that the computer reaches the Guild server.
- Right after the reset, two lines will say that the device has no identity and that the relay was not checked. That is expected: the computer is not activated yet. Open Guild and enter the new key.
- If the computer is activated with a new key and Guild still does not connect, send us the lines that mention connect.app.continental-c.com.
Terminal
Linux
getent hosts connect.app.continental-c.com
guild-host doctor- The first command must print the server address. An empty reply means the server name cannot be resolved: the network is in the way.
- The second prints a report in Russian, line by line. The line that mentions connect.app.continental-c.com and TCP :443 shows that the computer reaches the Guild server.
- Right after the reset, two lines will say that the device has no identity and that the relay was not checked. That is expected: the computer is not activated yet. Enter the new key with
guild-host activate --code. - If the computer is activated with a new key and Guild still does not connect, send us the lines that mention connect.app.continental-c.com.
No commands
iPhone and Android
Open your account in the phone browser
The address is guild.app.continental-c.com. If the page opens, the network reaches Guild.Check the computer
It must be switched on with Guild open: the phone works through the computer.Retry the check in Guild on the phone
If the connection still does not come up
Turn the VPN on or off, try another network and repeat the check. If that does not help, send us what the commands printed and tell us whether a VPN is on.
Frequently asked questions
- Are my agents and conversations gone?
- No. They are stored on your computer and are still there.
- Do I need to reinstall Guild?
- No. A new activation and an update are enough.
- The key does not work. What should I do?
- A key is valid for one hour and works once — request a new one. The phone needs a separate key from the phone tab.
- How many devices can I connect?
- One computer and one phone per account. The device list in the account is empty now, so there is nothing to revoke.
- The account does not recognise my e-mail. What should I do?
- Sign up with the same address and write to us.
- Why did Center notifications keep arriving during the outage?
- Guild fetches them from Center directly, not through our server.
- Guild says the server is not responding. What should I do?
- If the computer is not activated with a new key yet, start with step 2. If it is, go through the section on checking the connection to the server.
Need help
Message us on Telegram or at guild@morozov.digital. Tell us which device you use and what Guild shows — we will look into your situation. If your screen looks different from what is described here, tell us too.