Overview
The 3DPrinterOS Client has a local web interface that lets you manage printers, add new devices, update the Client, and adjust settings. This interface is separate from the Cloud login at cloud.3dprinteros.com.
When you access this web interface, you may need to pass through one or two login screens depending on how you are connecting. This article explains what each screen is for and what credentials to use.
Important: Logging out of the Client will stop the Client service, disconnect all printers, and interrupt any active prints.
Two Login Screens
The Client web interface has two login screens that serve different purposes. Depending on how you connect, you may see one or both of them.
Screen 1: Remote Access Authentication
This screen says "Please enter your 3DPrinterOS credentials or this image's SSH credentials." It appears when you access the Client from another device on the network using the host's IP address. Its purpose is to verify that you are authorized to access the Client's web interface.
This screen accepts:
The device's SSH username and password. These are the credentials used to log into the machine itself (via terminal or SSH), not a 3DPrinterOS account. On Raspberry Pi, these are provided in the email sent with your SD card image.
The Cloud email and password of the account the Client is currently running under. Only the credentials of that specific account will work. Other Cloud users' credentials will be rejected.
The text on this screen can be misleading. It says "3DPrinterOS credentials," but it does not accept just any Cloud account. Only the credentials of the account the Client is currently logged in with will work.
When you access the Client locally at localhost:8008 or 127.0.0.1:8008, this screen is skipped entirely because you already have direct access to the machine.
Screen 2: Client Cloud Login
This screen has Autologin, Offline mode, Email/Password fields, a "Forgot your password?" link, and a Sign up option. This is where the Client gets linked to a Cloud account.
This is a Cloud login screen. You can log in with any valid 3DPrinterOS Cloud email and password. SSH credentials do not work here.
If the Client is already logged in to a Cloud account, this screen is skipped and you go directly to the printers list.
How the screens work together:
From localhost (127.0.0.1:8008): Remote auth screen is skipped → Cloud login screen if Client is not logged in, or printers list if it is.
From remote IP: Remote auth screen first → Cloud login screen if Client is not logged in, or printers list if it is.
Enabling Remote Access
On Raspberry Pi images, the Client web interface is accessible from other devices on the same network by default. On Windows, macOS, and Linux installs, external access is disabled by default and must be enabled first. See Configuring HTTPS and External Access for 3DPrinterOS Client for instructions.
Raspberry Pi
On Raspberry Pi, the Client is linked to your Cloud account during the initial setup when the SD card image boots for the first time. Remote access is enabled by default.
To access the Client web interface from another device, open a browser on the same network and navigate to the Raspberry Pi's IP address on port 80 (HTTP) or port 443 (HTTPS). For example: http://192.168.1.100 or https://192.168.1.100. You will see the remote auth screen and can log in with the SSH credentials from your image email or the Cloud credentials of the account the Client is running under.
Windows
On Windows, the Client web interface automatically opens in your default browser at localhost:8008 after you start the application. During the first launch, the remote auth screen is skipped and you will see the Cloud login screen where you can log in with any Cloud account to link the Client.
If you need to access the web interface from another computer on the same network, you must first enable external access (see the Enabling Remote Access section above). After that, navigate to the host PC's IP address on port 443 (for example: https://192.168.1.50). You will first see the remote auth screen, then the Cloud login screen if the Client is not yet logged in, or the printers list if it is.
macOS
The macOS Client works the same way as Windows. The web interface opens automatically on first launch at localhost:8008, and you log in with your Cloud account to link the Client. Remote access from other devices requires enabling external access first.
Linux / Ubuntu
On Linux, the Client may be installed via a package or ZIP archive. If the machine has a desktop environment and a browser, you can access the Client at localhost:8008 and log in with any Cloud account, just like on Windows or macOS.
If the machine is headless (no monitor or browser available), you can link the Client to a Cloud account via the console login command described in the section below.
As with Windows and macOS, remote access from other devices must be enabled first if accessing the Client from a different machine on the network.
Console Login (All Platforms)
On any platform, you can link or re-link the Client to a Cloud account via a terminal command:
python3 <path-to-3dprinteros-client>/console_login.py
The path to the script and to python3 varies by platform and installation method. This command will prompt you to enter your Cloud email and password, linking the Client to that account.
This is especially useful for headless Linux machines where no browser is available, but it works on Windows and macOS as well.
Switching to a Different Cloud Account
To switch the Client to a different Cloud account, you can either log out through the local web interface at localhost:8008 and log in with the new account, or use the console login command described above.
Warning: Switching the Client to a different Cloud account will unlink all currently connected printers. They will need to be set up again under the new account.
Allowing Multiple Users to Access the Web Interface Remotely
The Client runs under a single Cloud account at a time. If another user needs to access the Client web interface remotely without changing the active account, they should use the device's SSH credentials on the remote auth screen. This allows them to view and manage printers without disrupting the current setup.