Beget reported that more than 50 000 websites were back up and that customers could issue SSL certificates for them themselves. For customers, this means some websites are already accessible, but the restoration of certain features and servers is still ongoing: the provider is restoring virtual hosting from backups, while the control panel is not yet fully operational.

Recovery here consists of several independent tasks. Restoring a website’s files to the server is not enough if the domain is not linked to the right directory or an SSL certificate has not yet been installed for HTTPS. So one website may already open, another may show a restoration notice, and a third may need its configuration checked in the control panel. There is no universal “everything’s back to how it was” switch yet.

What exactly Beget is restoring

The company reported that it had completed half of the work restoring data from backups and planned to finish the bulk of the virtual hosting recovery within three days. Beget separately cautioned that this was an estimated timeframe: it could change depending on how the work progressed. So this estimate should not be taken as a guarantee that every account will be restored by a specific time.

According to the provider, more than 50 000 websites are back up, while other servers are still being restored. This distinction matters to website owners: the total number of restored resources does not mean that a particular website is already accessible or that all its related features are working. The company said it would continue to keep customers informed about the progress and announce when the work is complete.

Sections and features are gradually being brought back in the control panel, but it is currently available in a limited mode. The provider also noted that its team is focused on restoration. For customers, this means that whether a particular operation is available may depend on whether the relevant part of the panel has been restored, not just on the state of the website’s files.

You can now issue SSL certificates yourself in the “Domains and Subdomains” section. This is useful when a website opens but the browser reports an SSL problem: according to Beget, a certificate needs to be set up again on a prepared new server, and issuing it may lag behind the website itself coming back online. In other words, the green indicator in the browser does not automatically come back the moment the pages reappear.

Customers can request certificate installation in the control panel. To do this, open the three-dot menu next to the domain, select “Manage SSL Certificates,” and then “Install Certificate.” Beget says installation may take up to an hour. The menu names are given as they appear in the provider’s instructions; access to the required section depends on the current state of the control panel.

The provider also recommends checking the link between the domain and the website directory in the “Websites” section. If management options are available there, customers can check the association and, if needed, change the PHP version. This does not replace restoring a backup: the check concerns settings that determine where the domain points and which PHP version the website uses.

How to interpret notices and errors

Beget says a notice that the domain is not linked is related to the restoration process: backups may still be uploading to the server. If the control panel shows that the account is being restored, the provider recommends waiting for completion or checking back later. If the “Websites” section is already available, check that the domain is linked to the right directory and wait for the website to come back online.

There is an important distinction here between a sign that a process is underway and confirmation of the result. A restoration notice does not mean the website is already fully operational; it indicates that the backup is still uploading. Likewise, the website being accessible does not confirm that SSL is configured, and being able to open the control panel does not mean all its features are back. Recovery is happening in stages, so these states may not match up.

If the pages are already opening but the website is showing errors, Beget suggests trying a different PHP version in the “Websites” section. To do this, open the settings using the gear icon and select the required option. This is the provider’s recommendation for this particular situation, not a claim that changing the PHP version will fix every error: the cause may be something else.

The most noticeable practical inconvenience is that the certificate, domain association, and files are not necessarily restored in sync. Manually checking several things is genuinely necessary right now; automation in this process is not yet pretending to be complete.

VPS backups and the incident context

VPS backups were temporarily removed from the control panel because of technical constraints. Beget said it was refining the system for providing them and working to restore the option to request a download link from the panel, as well as an alternative way to access them. The company promises to notify customers about changes. So VPS customers should not currently count on being able to get a backup through the usual interface.

The current work is related to a large-scale incident in Beget’s infrastructure. In earlier notices, the provider described a cyberattack on the night of 1 to 2 November 2026, access to the control plane, and the launch of scripts that wiped data. According to the information published at the time, data in the cloud infrastructure, including VPS, S3, and Kubernetes, was lost; VPS file backups were preserved. The company began rebuilding its cloud infrastructure, while virtual hosting is being restored from backups.

Beget previously reported that VPS file backups could be downloaded through the cp.beget.com control panel. The company is now separately talking about the temporary unavailability of backups in the panel and its work on ways to provide them. These notices describe different stages and options, so VPS customers should go by the current state of the interface and the provider’s next announcements, rather than assume access to backups is guaranteed.

For websites that have not yet come back, Beget provided the technical support address: [email protected]. The provider warned that, due to a high volume of requests, replies may take longer than usual. Other restrictions mentioned in the earlier context include the temporary suspension of Beget’s accreditation as a registrar for RU and РФ domains; the company cannot register new domains there or accept transfers from other registrars, but must continue supporting domains registered before the accreditation was suspended.

The most concrete step for owners of websites that are already accessible is to check SSL under “Domains and Subdomains,” and, if there are errors, check the directory association and PHP version in the “Websites” section. If the account is still being restored, Beget’s instruction is to wait for the process to finish; for VPS, access to backups through the control panel remains a separate unresolved issue.