DocsICP FilingConsole
Documentation
Home Page Object Storage Service Developer Reference Developer tools ossbrowser 2.0 (preview) Install ossbrowser 2.0

Install ossbrowser 2.0

Updated at:
Copy as MD
Product
My Favorites

This topic describes how to install ossbrowser 2.0 on Windows, macOS, and Linux.

Important

  • Requires Windows 7 or later, including Windows Server.

  • Linux x64 distributions vary in GUI dependencies. For optimal performance, use Windows or macOS.

Windows

  1. Click to download the Windows x86-64 installation package.

  2. Double-click the downloaded installation package, select an installation directory, and then click Install.

  3. Find the oss-browser2 application on your desktop and double-click it to open it. The AK Login page is displayed. Three login methods are supported: AK Login, Account Login, and Authorization Code Login. The AK Login method requires the following information:

    • AccessKeyID: Required. You can enter the value directly or select from history.

    • AccessKeySecret: Required. You can toggle the visibility of the secret.

    • Endpoint: The default value is Public Endpoint. You can select Use HTTPS.

    • Preset OSS Path: Optional. You can specify a bucket name and a file prefix.

    At the bottom, you can select Keep me logged in and Record Session, and then click Log On.

macOS

  1. Open a terminal window and run uname -m to check the system architecture. The arm64 architecture is used in this example.

  2. Download the installation package that matches your system architecture:

  3. Double-click the downloaded package to open it.

  4. Drag oss-browser2.app to the Applications folder as prompted.

  5. Open Launchpad, find the oss-browser2 application, and double-click it to open it.

    1. If a security warning appears, click Open to proceed.

    2. The AK Login page is displayed with the following configuration items:

      • AccessKeyID: Enter or select an AccessKey ID.

      • AccessKeySecret: Enter an AccessKey Secret.

      • Endpoint: Select an endpoint type. The default value is Public Endpoint. You can select Use HTTPS.

      • Preset OSS Path: Prefixed with oss://. You can optionally specify a bucket name and a file prefix.

      • You can select Keep me logged in and Record Session, and then click Log On.

Linux

Important

ossbrowser 2.0 cannot be run as the root user. You must log on to the system as a non-root user to use ossbrowser 2.0.

The following example uses Ubuntu 22.04.

  1. Install a graphical user interface (GUI).

    Run the following commands to install a GUI. For instructions on how to install a GUI on other Linux distributions, see Install a GUI on a Linux instance.

    sudo apt-get update
sudo apt-get install ubuntu-desktop
reboot

  2. Log on to the system as a non-root user.

    After you install a GUI on an ECS instance, restart the system and use VNC to connect to the GUI. In the Connect via VNC dialog box that appears, click Log On Now.

  3. Download the installation package.

    wget https://gosspublic.alicdn.com/oss-browser2-prod/2.2.0/oss-browser2-linux-x86_64-2.2.0.AppImage

  4. Install ossbrowser 2.0.

    1. Right-click the downloaded installation package and click Properties.

    2. Click Permissions and turn on the Execute toggle to allow the file to be executed as a program.

    3. Double-click the ossbrowser 2.0 package to open it. The login page is displayed with three login method tabs: AK Login, Account Login, and Authorization Code Login. Select AK Login and enter AccessKeyID and AccessKeySecret, and select an Endpoint. The default value is Public Endpoint. You can select Use HTTPS. You can also configure a preset OSS path with a bucket name and a file prefix, and select Keep me logged in and Record Session.

FAQ

Cannot start ossbrowser 2.0 on Ubuntu 22.04

  • Issue: If you encounter the following error message when starting ossbrowser 2.0, the issue is usually caused by the Chromium sandbox within the AppImage application requiring specific permissions to run properly, and the current user does not have the required permissions.

    xxx@iZxxx:~/Desktop$ ./oss-browser2-linux-x86_64-xxx.AppImage
[7849:0709/103133.830504:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now.
You need to make sure that /tmp/.mount_oss-brQeJ8RW/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

  • Solution: You can install the AppImageLauncher tool, which automatically resolves permission and dependency issues for AppImage applications when you start ossbrowser 2.0 again. The following steps show how to download and install AppImageLauncher.

    # Download AppImageLauncher
sudo wget https://github.com/TheAssassin/AppImageLauncher/releases/download/v2.2.0/appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64.deb

# Install AppImageLauncher
sudo apt install ./appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64.deb

What to do next

For information about how to log on to ossbrowser 2.0 and its configuration items, see Log on to ossbrowser 2.0.

Previous：ossbrowser 2.0 (preview)Next：Log on to ossbrowser 2.0