Hva er nytt

På denne siden publiseres AtlasPVE-versjonsnyheter, gjennomganger av Proxmox-oppdateringer og utvalgte nyheter fra serververdenen. Eksisterende funksjoner presenteres etter tur; siden oppdateres jevnlig.

Atlas Link and Docker apps

Atlas-versjon ·

Update the Atlas Link connector from the Updates page after updating Atlas. With changelog translation enabled, you can read Atlas Link connector release notes in your interface language. Choose a connected data disk for application data when installing through the LXC wizard or the store. Follow Docker application installation progress and current status, and access applications by their local network names. An installed Docker app’s data can be moved to another attached disk with visible progress. The previous copy is kept for recovery.

Atlas Link update progress

Atlas-versjon ·

Follow Atlas Link connector updates in the shared installation window, with visible steps and results.

AtlasPVE 1.205 released: an instant alert when a machine is shut down for lack of memory

Atlas-versjon ·

When a virtual machine is shut down because the server ran out of memory, Atlas Watch sends a critical alert with the machine's name right away. The new container wizard also installs app containers with non-root Proxmox accounts. The Secure Boot setting is available to accounts with disk configuration permission in Proxmox. Atlas Link no longer opens needless connections to the server's service for visitors whose connection has dropped. Permission checks were strengthened.

AtlasPVE 1.203 released: graphics card issues on Windows, memory warnings and Portainer

Atlas-versjon ·

If a graphics card given to a virtual machine does not work inside Windows, for example with Code 43, Atlas Watch reports it with the reason and offers buttons to resolve it. When an NVIDIA card is given to a Windows machine, Atlas writes the required CPU setting by itself; for cards given earlier, the Hardware passthrough page shows the state and fixes it with one button. On machines with passed-through devices, the wizard and the memory window warn in advance whether memory will still be enough when other machines grow. When a machine is shut down because memory ran out, the Memory page shows which machine it was. A half finished snapshot that locks a machine is cleaned up with one button. The console fits the window every time it opens. Docker Engine, Portainer CE and Portainer Agent arrived in the Store; apps that need full privileges ask for explicit confirmation before installation. The new machine wizard checks the machine name in the step where it is typed, and password fields start hidden. Accounts with console permission in Proxmox can open the machine console from Atlas, and permission checks now take Proxmox pools into account.

AtlasPVE 1.186 released: completing interrupted package installs and a guest agent warning

Atlas-versjon ·

If a package install was interrupted, for example by a power outage, updates first complete the unfinished operation and the server keeps updating from the panel. The interrupted operation appears in Atlas Watch and can be completed with one button. Atlas Watch reports running virtual machines whose guest agent is missing or not responding, and points to the agent installation. If a machine is deleted or rolled back while Browse is open, the session closes by itself and the disk is fully cleaned up on the server. While installing a Docker app, machines without Docker Engine are listed in a separate section and the Engine can be installed from there with one button. Store apps can also be installed on Debian 12 machines. Permission checks were strengthened.

AtlasPVE 1.185 released: editing files on running machines with Browse and a new container wizard

Atlas-versjon ·

To write to the disk of a running machine, Browse can shut the machine down with one button or open the disk from inside the machine. Text files are edited directly in the window with the Edit button on their row. When the server does not have enough memory, Browse does not open and explains why. In the new container wizard, CPU, memory and disk are set in separate steps with sliders, just like the virtual machine wizard, and separate mount points for data can be added to the container. When an app is installed, the time zone comes from the server's own time zone. Search in the system logs now covers every log entry, and the screen updates right away when storage content types are saved.

AtlasPVE 1.184 released: import from VMware ESXi, per machine firewall and container features

Atlas-versjon ·

Virtual machines on a VMware ESXi server connected to Proxmox can be imported into Proxmox with a single wizard from the storage screen. ESXi storages appear on the storage screen and in the maps. The firewall rules of individual virtual machines and containers are managed from the Network tab, where a container's DNS settings can also be changed. Container features such as Nesting, NFS, SMB and FUSE can be switched on and off from Atlas. While creating a container the type and free space of each storage are shown, and new LXC templates download from the Store with one click. For actions that cannot be undone, the confirmation text is now a short identifier that can be copied with a double click. Atlas does not touch the Proxmox subscription notice. When updates stop because of the enterprise repository, the options to enter a subscription key, get a subscription from Proxmox or move to the free repository are offered. Repairing boot files reports the reason when it cannot complete, and progress is shown on screen while Atlas is being removed.

AtlasPVE 1.180 is out: Workspace and AI connection

Atlas-versjon ·

The new Workspace page brings services and machine consoles together as tabs; added services open without leaving Atlas. Workspace finds the web interfaces on machines by itself: Docker apps, addresses written in machine notes and web services running on machines appear with their own logos and are added with one click. The icon picker has thousands of real app logos. A user's own AI client can connect to Atlas read only over MCP; the connection key is created and revoked in the AI section of Settings. Atlas does not provide an AI service; questions are answered by the client and model the user chooses. When defining a custom app in the Docker store, a docker run command can be pasted and Atlas turns it into a compose recipe. The panel opens faster, and every page loads completely on busy servers too. The update is installed from the Updates screen in Atlas.

AtlasPVE 1.174.6 released: Docker app updates in a single flow

Atlas-versjon ·

Docker app updates now refresh dependent services and Compose override files together in a single flow, then verify the health of the project. The Atlas update history clearly shows the starting and target version of every install.

AtlasPVE 1.174 is out: updates run step by step in a window, background jobs on one screen

Atlas-versjon ·

Atlas updates now run step by step in a window and appear in the task list; the update keeps running in the background even if the window is closed or another page is opened. The Reboot now button on the Updates page now uses the confirmed restart step; the server restarts after identity verification. The Background screen in Settings now also shows panel certificate renewal, the update check, license sync and the Atlas Watch timer sync. Atlas Watch reports background jobs that do not run on time or fail repeatedly in the daily summary and in the Control Center. The Updates section in Settings is split into Preferences, Sources and Scheduled updates sub tabs. Values entered in Docker store app settings are checked before installation, and VM and container updates are read and installed more reliably. The previous release started updating Docker store apps without waiting for an Atlas update and redesigned the Atlas Watch daily summary email. The update is installed from the Updates screen in Atlas.

AtlasPVE 1.160 is out: Atlas Watch keeps an eye on backups and machine health

Atlas-versjon ·

Atlas Watch now also watches backups and snapshots: a machine without regular backups, a failed or unverifiable backup, backups that pile up because no retention is set, a stuck lock and an unfinished snapshot appear on the Backups page and in the Control Center; the lock and the unfinished snapshot are cleaned up with the card's own button. Backup job retention is set from Atlas, and before saving it shows how many old backups will be deleted. Machine health is watched too: a machine that stopped on a disk error, crashed, was shut down because memory ran out or no longer responds, and a machine that has been waiting on processor, disk or memory for a long time appear in the Control Center. Image updates for Docker containers appear on the Updates screen; containers set up with compose are updated after a snapshot of the machine is taken. On Windows machines, optional and driver updates can be installed too. Store apps come with their network settings ready. The previous release started installing updates inside virtual machines and containers from Atlas; the Processor and Memory pages show the processes inside machines, the Docker store receives new apps without waiting for an Atlas update, and the interface is also available in Traditional Chinese. The update is installed from the Updates screen in Atlas.

AtlasPVE 1.161 and 1.169 released: permission security, the Docker store and a refreshed Watch digest email

Atlas-versjon ·

A permission gap that allowed read-only accounts to make some write requests was closed, and those requests are now recorded in the audit log. Saving a retention setting that would delete backups now asks for identity confirmation. Installing this update is recommended. Apps in the Docker store can be updated without waiting for an Atlas update, and ownCloud Infinite Scale was added. Several apps with their own addresses can be installed on the same machine, and links to apps that require HTTPS open correctly. The security scan also checks the environment files an app reads. The Atlas Watch daily digest email was refreshed: severity counts at the top, every section in the same card and a severity badge on every line. If an email sent from the server is rejected by the recipient, Watch reports it with the reason. On the Background screen in Settings every task can be run, paused and given a different frequency.

AtlasPVE 1.149 released: updates inside machines, process management and Traditional Chinese

Atlas-versjon ·

Updates inside virtual machines and containers can now be checked and installed from Atlas. A snapshot is taken before installation and updates are grouped the same way as on the server. On the CPU and Memory pages, clicking a machine shows the processes inside it, which can be managed there, on Linux and Windows. The Background tab under Settings, Atlas Watch shows the tasks Atlas runs by itself together with their last runs. Hardware passthrough can give a single physical disk to a virtual machine. The network name of machines and Docker apps can be changed. Storage usage is shown more accurately and Atlas Watch has a usage card. On Windows machines with a passed-through graphics card, the console keeps the picture from boot to the login screen. The Docker store receives new apps without waiting for an Atlas update, and installs pass a security check. The interface is now also available in Traditional Chinese.

AtlasPVE 1.125 is out: Atlas Watch on every page, the console understands graphics cards

Atlas-versjon ·

Atlas Watch monitors Memory, Processor, Storage, Hardware passthrough, Docker and LXC findings even when the page is closed. Control Center groups each area in its own tab; alarm rules are set up from ready templates, and wearing disks and nearly full virtual machine disks are reported in advance. On Windows machines with a monitor on the graphics card, opening the Atlas console turns the card's displays off temporarily and the console shows the virtual display; closing the console brings the card's displays back in their previous layout. Docker apps with a graphics card keep starting on the card after kernel updates; when the card cannot be used, Atlas Watch states the reason and what to do. The Hardware passthrough page sets up protection for devices that could lock up the server by itself. Atlas Link moved to its own page in the left menu; the Updates screen sorts packages into four groups and tells which services a package will restart. The new machine wizard guides the memory, processor and graphics card steps. A check request sends only package names and versions. The update is installed from the Updates screen in Atlas.

AtlasPVE 0.911 to 0.914 released: one click Atlas updates and installs that complete themselves

Atlas-versjon ·

Atlas updates now start from the panel with one click. A note below the button says, before it is pressed, that the connection may drop for a few seconds. An install in progress no longer disappears when the page is refreshed; its state is read from the machine. If the install has not started, the screen says so right away and offers repair in the same box. Repair installs the version already delivered to the machine, so an interrupted install can be completed from there. With an optional switch, an update started from the panel that does not complete reports back. The switch is on the Update tab in Settings, and nothing is sent while it is off.

AtlasPVE 0.910 released: the delete protection flow and container screens

Atlas-versjon ·

When an operation cannot be carried out, the reason is written on screen. Cases such as delete protection being on, another operation holding the machine locked, or snapshots using the disk are named, and they read in the language of the panel. On a machine with delete protection on, this is said before identity is asked. The window that opens carries the name of the machine, where the setting lives and a single button that removes the protection; once it is removed, the delete confirmation continues from where it left off. Container screens are drawn for containers. Cards, fields and buttons that only have a counterpart on a virtual machine do not appear on a container. Containers now have their own options window; start on host boot and delete protection are changed from there. Shutting down, deleting, rolling back to a snapshot and deleting a snapshot were fixed on containers as well. The operating system family and the boot order were added to the boot options. The order is built by selecting and moving devices; fields that are not written in the configuration appear as default. Touching a value row on the configuration card opens the related editor. The watchdog also follows network packet drops. The threshold is the number of drops per minute; the measurement is a fifteen minute average, so a momentary fluctuation produces no notification. Package compatibility information can also be refreshed without waiting for a new version.

Package compatibility now refreshes without waiting for a release

Atlas-versjon ·

Next to every package on the updates screen there is an evaluation that says what will happen: whether it installs without interruption, whether a service restarts, or whether the machine needs a restart. Until now that evaluation shipped inside the product, so refreshing it required a new Atlas version. Debian and Proxmox release packages on their own calendar though, and what a package does has nothing to do with the Atlas version. The evaluation can now be refreshed separately through a signed document. On installations with internet access, measured information for packages arrives on its own and the badges follow it, with no release to wait for. The document is verified with the key embedded in the product, and a document that fails verification is ignored entirely. The rule is one way: a document can only fill in missing information or raise a warning, never lower one. The worst case is an extra warning, never a hidden interruption. A lighter evaluation is applied only with a new Atlas version, and the screen says that it is waiting for one. On offline installations nothing changes: the built in table remains in effect and the cautious label stays until the next release. In the same round the updates list also got faster, as it no longer waits for the network.

AtlasPVE 0.907 released: the installation store, and identity on machine access

Atlas-versjon ·

The installation store has arrived. What installation material is at hand, how much space it takes, whether its integrity is verified and which version is installed on which machine are now on one screen. Returning to the version that came with the installation is done from here as well. If a required installation file is not in the store, the server downloads it once, puts it into the store and verifies it against the expected fingerprint. The same file is no longer downloaded again for every machine, and later machines can be set up without any internet access. The images of an installed application can also be taken into the store and installed on another machine offline. Identity moved to the front of machine access. The terminal greets with the login screen of the machine itself: the username and password are asked on the machine and Atlas stores no password. The file browser window asks for the username and password of the machine before it opens. Both surfaces carry a duration setting on their card: ask every time, or do not ask for 1, 2 or 4 hours. Neither the terminal nor the file browser leaves an open port on the network; both are reached only from inside the server. Installations inside a machine now stream live. A notification appears when an installation starts and opening it shows the command output line by line; the work is not lost when the page is refreshed and the same installation is not started twice. The steps of the flow and the result and error sentences are written in the language of the panel. Restarting and applying pending changes were added to the operation list on the Settings screen; a simple confirmation or a password protected confirmation can be chosen for each operation.

AtlasPVE 0.865 released: in-machine services on every machine, agent setup from the page

Atlas-versjon ·

The Terminal, Console and File browser on the virtual machine page now open more reliably on every machine. When a prerequisite is missing the window stays open; the missing step is shown in order inside the same window, the setup starts from there, and the window continues on its own as each step completes. QEMU Guest Agent setup has moved onto the page as well. On a machine created by the wizard a single button is enough; on machines created outside the wizard Atlas installs it using the machine's own SSH account, and the machine's address is found on the network and filled in automatically. On Windows machines the virtio-win ISO is attached with a single button, and a manual guide for Linux and Windows lives inside the card. On machines with a serial console, the console now opens on the new Proxmox version too, the login prompt appears immediately, and it no longer drops after two hours in long sessions. The smart suggestions list no longer flickers while refreshing.

AtlasPVE 0.861 released: console inside the panel, tabbed updates screen

Atlas-versjon ·

The console and terminal of a virtual machine now open inside the panel. The console each machine supports is selected automatically: a serial console on machines installed from cloud images, a graphical console on machines with a display. In guest services are installed from the panel as well, and each one shows its state on its own button: web terminal, file browser, metrics probe. The updates screen is split into tabs. Pending packages, smart suggestions and update history each have their own tab; selecting a package in the list opens that package on its own page, and the list has search and filtering by impact. The smart suggestions panel now has the same layout on every screen: cards fold, urgent ones stay open, the panel can be collapsed and the collapsed state is remembered. A web terminal can be selected while creating a machine and the selected packages are listed in the summary step. Memory can be changed while a machine is running, and where a restart is required the card states which setting can be changed to avoid it. Shutting down a machine or a container asks for confirmation, and the weight of that confirmation is set on the Settings screen.

AtlasPVE 0.838 to 0.844 released: improvements to memory, cluster and container screens

Atlas-versjon ·

When the balloon minimum in the memory settings is set below the machine's current usage, the screen now states the outcome beforehand. Memory settings that have no effect on a machine with a passed-through device are no longer offered during machine creation. The cluster screen describes the state of a single server correctly in one sentence. The container hardware card shows only the settings that apply to containers. Certificate dates, status information and cluster descriptions now appear in the selected interface language.

AtlasPVE 0.810 released: two-step verification is managed from the panel, and user and permission management is complete

Atlas-versjon ·

Two-step verification is now managed inside Atlas. Authenticator codes, recovery keys, hardware keys and Yubico OTP records are added and removed from the user card, and the registered methods are visible at a glance. The sign-in screen explains the second step: it lists which methods are available, states when the authenticator code is locked after repeated wrong attempts, reports a registered method that was left out of the list, and never shows a field for a code that could not be accepted. User management is complete: roles, permissions and groups are handled from one screen, group creation and membership were added, the access map shows who receives which permission through which path, and the screen points out what can be tidied in the permission layout. Irreversible operations ask for identity again: deleting an account, a role or a group, changing a password and removing a second-factor record all ask for the password and the second factor, and the consequence is stated with figures. Containers now match virtual machines; they are listed in the side menu, have a map view, and are created through a step-by-step wizard. The store also carries operating system templates, which are downloaded from the catalogue and used to create containers directly, with the card reporting when a newer version appears.

AtlasPVE 0.830 released: the update flow and package repository management were reworked

Atlas-versjon ·

The update flow was reviewed end to end. A new Atlas version appears at the top of the Updates page rather than having to be looked for. The outcome of an installation is read from the machine's own record and reported correctly on screen; if an installation finishes after you leave the page, the outcome is still recorded in the notifications. The installation history also shows the outcome correctly. Package repository management now works. The repository list comes from what the machine actually offers, repositories are enabled and disabled in one place, and a subscription key can be saved. When the package list cannot be refreshed because of a repository that requires a subscription, the screen names the cause and offers two ways forward: switching to the free Proxmox repository or entering a subscription key. The choice can be changed later. Removal and repair are also confirmed in the product's own dialog with the consequence stated plainly, and notifications state what happened rather than technical detail.

AtlasPVE 0.835 released: live memory on machines with PCI passthrough

Atlas-versjon ·

On virtual machines with a PCI device passed through, memory can now be grown and shrunk while the machine keeps running. The memory dialog adapts to the machine: on a machine whose memory is pinned by a device the balloon setting is not offered; a live memory switch takes its place, and the dialog says which setting will work. The live memory setting only accepts valid memory sizes. When a size that would prevent the machine from starting is chosen, saving stops and the two nearest valid sizes are offered with one tap; if such a size was saved earlier, the panel warns before the machine is started. Growing the memory is not saved when the host does not have enough free memory, and the reason is explained with numbers. Memory advice also follows the real behaviour of these machines; a machine with pinned memory no longer shows a misleading usage warning.

AtlasPVE 0.661 released: update results confirmed by version, and the pre-flight check recognizes our own service

Atlas-versjon ·

While installing its own update, Atlas could report the result incorrectly: the installation completed but the screen showed a failure, or it waited at the restart step and returned to the beginning. The result is now decided by the version the server reports after the restart: matching the target means done, returning to the previous version means rolled back, and no answer in time is reported as unconfirmed. When the update finishes, the panel refreshes itself so the new interface arrives at the same time. On some systems the pre-flight check did not recognize that the process holding the panel port was Atlas itself, and the installation never started. The check now identifies the process by whether it belongs to the Atlas service rather than by its name; if a foreign service holds the port, the installation still stops and says why. The license screen was reworked in this release as well: the linked portal account, the idle licenses in that account and the server capacity are shown on one screen, and a server is linked by signing in with an email address from the panel.

AtlasPVE 0.650 released: reworked firewall card, network settings that repair themselves

Atlas-versjon ·

The firewall card on the network page has been reworked. The rule list now follows the file on the server line by line, disabled rules stay visible, and deleting a rule asks for confirmation and names the rule that will be removed. A rule that allows management access raises an extra warning. Name checking for virtual switches and bonds now covers every interface name in use on the machine as well as network configuration that has not been applied yet, so the suggested name is one that is genuinely free. When a name is rejected, the reason is shown on screen. A half finished network operation can no longer leave the server unable to apply its network settings. The product recognises that state, repairs it on its own and completes the requested operation. The network map opens at a readable scale on phones and tablets, can be panned sideways, and the centring buttons switch between an overview that fits every column on screen and the readable view. The wording on the network screen has been simplified as well: instead of technical abbreviations it says what is being done and what the result will be.

AtlasPVE 0.647 released: network management from the panel, reworked setup flow

Atlas-versjon ·

The Network page was rebuilt. List and map live on the same page and the details of anything selected open in the same card; selecting a machine reveals its full path to the gateway, and the flow markers reflect real traffic. Address settings of virtual switches, SDN zones and virtual networks can now be managed from the panel. On servers with more than one network path, the interface the panel is reached through can be changed as well. In all of these, the lines that will change are shown before anything is applied, and without confirmation afterwards the previous state is restored automatically. The new virtual machine flow was reworked: a copy can be made from an existing machine, the target storage can be chosen, selected applications are installed onto the copy too, and locally defined Docker applications can also be picked from the store. When applications are selected, processor, memory and disk values are calculated to cover all of them together. The hardware passthrough screen lists by name what will be affected before a device is handed to a virtual machine. Credential files produced during installation are stored so that only the administrator account can read them; files left from earlier installations are brought to the same form by this update.

AtlasPVE 0.631 released: pre-installation environment check

Atlas-versjon ·

Installations and updates now verify that the server is suitable before they start: processor architecture, system services, the panel port, the cluster directory and disk space are measured up front. If something blocks the operation it does not start at all, the reason is printed on screen and a summary that can be copied for support is provided. Messages shown during installation appear in the language of the panel. Going to the panel address over plain HTTP is redirected to the secure connection, and access by local network name (.local) no longer produces an extra certificate warning.

AtlasPVE 0.620 released: session security hardened

Atlas-versjon ·

Idle sessions are now closed after a set period, with the reason shown on screen. The timeout can be adjusted or disabled from the Session card in Settings. In addition, when an update step cannot complete, the reason is now explained in the panel language.

Feature spotlight: Docker management

Funksjon i fokus ·

Docker workloads have their own page in the panel: containers are visible in one place, can be installed from the store, and resource usage can be monitored. The full story is on the Docker page.

Detaljer

AtlasPVE 0.584 to 0.587 released: Memory, hardware passthrough and Motherboard pages, and a Certificate tab

Atlas-versjon ·

Three new pages arrived. The Memory page shows how much memory each machine holds and how much can be reclaimed, as a list and as a map. The PCI and USB passthrough page shows which device is given to which machine, why it cannot be given when it cannot, and draws the isolation groups. The Motherboard screen shows memory and PCI Express slots in their real layout. The Storage page also gained list and map views. Settings has a Certificate tab: the owner, domain names and remaining days of the certificate the panel serves are visible. Certificates on the server can be selected with one click and a custom certificate can be installed from a file path or by pasting it, without any restart. The panel now serves the same certificate as Proxmox. A ready configuration example is included for setups behind a reverse proxy. The Privacy tab lists every outbound connection from the server in one place, all switched off by default. The Compatibility page shows which packages have been measured with this release. The Updates screen was simplified and now reports the result of an install by asking the system.

Compatibility verified with Proxmox VE 9.2.6

Proxmox ·

Updates published on the Proxmox side are reviewed on a regular basis. The latest review round was completed on August 15: package behavior was measured on Proxmox VE 9.2.6 and the product is aligned with this release.

AtlasPVE 0.452 released: a dedicated virtual machine wizard and reworked app installation

Atlas-versjon ·

Creating a new virtual machine now opens on its own page. The steps sit in a fixed list on the left, the card starts empty and every choice is made deliberately. The operating system list grew to 16 entries, including older Windows and Windows Server releases. Two industrial profiles were added for field servers and engineering workstations. App installation opens on its own page and every app in the App Store can be chosen from the wizard. Settings are asked during installation, passwords left empty are generated randomly and apps arrive with a pinned version. How the app connects to the network, whether it keeps running and which disk holds its data are chosen during installation. Apps made of several containers can be installed as well. Deleting a firewall rule or switching it on and off is now actually applied on the server. The network interface name is read from the server. Uppercase headings in the Turkish interface are fixed as well.

AtlasPVE 0.422 released: new virtual machine card, disk health monitoring and Hungarian

Atlas-versjon ·

Creating a new virtual machine no longer opens a separate window; it opens inside the Virtual Machines page. The card has six short sections: method, source, identity, hardware, network and summary. After a one click choice the next section opens by itself. Suggestions at the top of the card warn when the disk does not fit the storage or when the cores and memory exceed the server's capacity. Atlas Watch now also monitors disk health. If a disk fails its own health test it appears in the daily digest by device name; disks that report no health data produce no warning, and sleeping disks are not woken up needlessly. The interface is now also available in Hungarian, including date and number formats. Atlas now speaks 14 languages.

AtlasPVE 0.413 to 0.416 released: container detail page, alerts on the phone and more dependable updates

Atlas-versjon ·

Containers now open in the same detail page as virtual machines: snapshots, backups, network, console and configuration in one place, together with container specific fields. User passwords can be changed through Atlas. The interface is also available in Polish. Atlas Watch can send critical alerts to the portal account and to the phone; if the server stays silent for a long time the portal raises an alert, even when the server is completely down. Watch now also checks backup age, storage pool health and Proxmox core services. The Watch screen shows whether the last digest reached the portal. The Updates screen was reworked from top to bottom: each package shows what will happen when it is installed and how reliable that information is. Pre-flight checks now really protect, and whatever blocks an install is stated clearly before the Install button is pressed. Package pinning files are visible in Repository Management. Signing out now also closes the session on the server, ZFS pool alarms actually fire and removing Atlas leaves nothing behind on the machine.

AtlasPVE 0.396 released: container file manager and a security scan before installs

Atlas-versjon ·

Every file inside a container can now be viewed and edited from the panel; the file browser installs on the machine with one click. The App Store and install wizard set up ready-made apps in a single step, and if no suitable machine exists Atlas creates a lightweight one by itself. Every pasted Compose definition and install script is scanned on the server before it is installed, and risky lines require explicit confirmation. When a new Proxmox kernel series is released, Atlas reports it and verifies the result after installation by itself. LXC containers appearing stopped on Proxmox 9, connection errors while the panel restarts and screens waiting forever on stuck operations were fixed. This release also tightened session and permission checks, the audit log, file permissions, console connections and the integrity of update packages from end to end.

AtlasPVE 0.388 released: Docker management and the App Store

Atlas-versjon ·

Docker is now part of Atlas. The Docker page in the left menu lists every app running in virtual machines and LXC containers: what runs on which machine, which ones are up and which ports they listen on. Starting, stopping and restarting are one click away in the list. An app's detail page shows live CPU, memory and disk charts, ports, mounted folders, environment variables, logs and suggestions; the CPU share and memory limit can be changed even while the app is running. The App Store is open. Immich, Jellyfin, Pi-hole, Vaultwarden, Uptime Kuma and File Browser install with one click, either on an existing machine or on a new virtual machine created on the spot. The map view shows the flow from server to machine to app on one screen. An app can take its own address from the router and be found on the network by name, for example files.local. The Docker page also opens faster now: machines are scanned in parallel and the last known list is shown without waiting.

AtlasPVE 0.368 released: Russian interface and a License tab

Atlas-versjon ·

Atlas is now available in Russian as well. With this release the interface speaks 12 languages: Turkish, English, German, French, Italian, Spanish, Portuguese (Brazil), Dutch, Swedish, Norwegian, Danish and Russian. The language can be changed from the menu at any time. Settings has a new License tab. The server's license status, capacity and update entitlement are shown on a single screen.