Skip to content

Neko #1688

Closed
Closed
Neko#1688
Labels
Migration To ProxmoxVE

Description

@MickLesk
MickLesk
opened on Apr 13, 2026

Name of the Script

Neko

Script Type

CT (LXC Container)

📋 Script Details

a self-hosted virtual browser that runs in Docker and uses WebRTC technology. Neko is a powerful tool that allows you to run a fully-functional browser in a virtual environment, giving you the ability to access the internet securely and privately from anywhere. With Neko, you can browse the web, run applications, and perform other tasks just as you would on a regular browser, all within a secure and isolated environment. Whether you are a developer looking to test web applications, a privacy-conscious user seeking a secure browsing experience, or simply someone who wants to take advantage of the convenience and flexibility of a virtual browser, Neko is the perfect solution.

Image

Activity

  1. MickLesk
    added
    Ready For Testing
    on Apr 13, 2026

  2. github-actions commented on Apr 13, 2026

    @github-actions
    github-actionsBot
    on Apr 13, 2026 – with GitHub Actions
    Contributor

    The neko script is ready for testing:
    bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/neko.sh)"
    Default credentials:
    Password: admin

    Login is password-only: 'admin' for admin, 'neko' for regular user. Change both in /etc/neko/neko.yaml.
    Firefox ESR is installed as the default browser. The virtual display runs at 1280x720.

    Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

  3. forke24x7 commented on Apr 14, 2026

    @forke24x7
    forke24x7
    on Apr 14, 2026
    Image Installation completes with no error (as far as I can tell). However, when I try to open it nothing happens (ERR_CONNECTION_REFUSED). Using advanced setup because of static IP (only IPv4, as I do it in all other LXCs aswell).

    How can I contribute more? Full Verbose Log?

    Edit: Double checked obvious networking things - IP is not in use, tried different ip, IP is not in dhcp range, gateway and dns is correct and works in other LXCs without issues. I'll try on different proxmox host in different network soon.

    Edit 2: Tried with default settings, so using a dhcp ip - nothing changed, still not reachable.

    ⚙️ Using Default Settings on node pve
    💡 PVE Version 9.1.6 (Kernel: 6.17.4-2-pve)
    🆔 Container ID: 118
    🖥️ Operating System: debian (12)
    📦 Container Type: Unprivileged
    💾 Disk Size: 12 GB
    🧠 CPU Cores: 4
    🛠️ RAM Size: 4096 MiB
    🚀 Creating a Neko LXC using the above default settings

    ✔️ Storage local (Free: 68.7GB Used: 20.6GB) [Template]
    ✔️ Storage local-lvm (Free: 565.2GB Used: 229.2GB) [Container]
    ✔️ Storage 'local-lvm' (lvmthin) validated
    ✔️ Template storage 'local' validated
    ✔️ Template search completed
    ✔️ Template debian-12-standard_12.12-1_amd64.tar.zst [local]
    ✔️ LXC Container 118 was successfully created.
    ✔️ Started LXC Container
    ✔️ Network in LXC is reachable (ping)
    ✔️ Customized LXC Container
    ✔️ Set up Container OS
    ✔️ Network Connected: 172.20.20.51
    ✔️ IPv4 Internet Connected
    ✖️ IPv6 Internet Not Connected
    ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) git.community-scripts.org:(✔️ )
    ✔️ Updated Container OS
    ✔️ Installed Dependencies
    ✔️ Installed Build Dependencies
    💡 Failed to update npm to latest version (continuing with bundled npm 10.9.7)
    ✔️ Setup Node.js 22
    ✔️ Setup Go 1.26.2
    ✔️ Deployed: neko (3.1.0)
    ✔️ Built Client
    ✔️ Built Server
    ✔️ Set up Runtime
    ✔️ Created Service
    ✔️ Customized Container
    ✔️ Cleaned
    ✔️ Completed Successfully!

    🚀 Neko setup has been successfully initialized!
    💡 Access it using the following URL:
    🌐 http://172.20.20.51:8080

  4. GuiltyFox commented on Apr 15, 2026

    @GuiltyFox
    GuiltyFox
    on Apr 15, 2026

    after installed, it's need to stop and disable supervisor to make neko worked

    systemctl stop supervisor
systemctl disable supervisor
systemctl restart neko

    Note: If you changed ip after installed, you need to update new ip in /etc/neko/neko.yaml webrtc->nat1to1

  5. forke24x7 commented on Apr 15, 2026

    @forke24x7
    forke24x7
    on Apr 15, 2026

    Can confirm, another fresh advanced install (just static IP). After install it didnt work as expected. Disabling supervisior fixed the problem, neko is working now.

  6. CerberusStyle commented on Apr 15, 2026

    @CerberusStyle
    CerberusStyle
    on Apr 15, 2026

    Install completes, but i can confirm web interface fails until fix above is applied.

    update functions as expected.

  7. MickLesk commented on Apr 17, 2026

    @MickLesk
    MickLesk
    on Apr 17, 2026
    MemberAuthor

    fixed, try again

  8. forke24x7 commented on Apr 17, 2026

    @forke24x7
    forke24x7
    on Apr 17, 2026

    Can confirm, using advanced install with static ip config is working now

  9. smvb64 commented on Apr 23, 2026

    @smvb64
    smvb64
    on Apr 23, 2026

    Hello I can confirm the script is working

    I was discussing this over on Discord and had a quick question, would it be possible to add hardware acceleration support to the script?

    Neko supports three modes: no hardware acceleration, Intel hardware acceleration, and NVIDIA hardware acceleration. Adding this would be a huge improvement, as the current setup is quite taxing on the CPU.

    Would be similar to Plex LXC HW acceleration

    Best,
    Sm

  10. MickLesk commented on Apr 23, 2026

    @MickLesk
    MickLesk
    on Apr 23, 2026
    MemberAuthor

    Just Run it with var_gpu=yes bash....
    Before and Test it?

  11. smvb64 commented on Apr 23, 2026

    @smvb64
    smvb64
    on Apr 23, 2026

    Just Run it with var_gpu=yes bash.... Before and Test it?

    I'll test it and let you know thanks

  12. MickLesk commented on Apr 25, 2026

    @MickLesk
    MickLesk
    on Apr 25, 2026
    MemberAuthor

    added now as default

  13. MickLesk
    added
    Migration To ProxmoxVE
    and removed
    Ready For Testing
    on Apr 30, 2026
  14. github-actions
    locked as resolved and limited conversation to collaborators on Apr 30, 2026

  15. michelroegl-brunner commented on Apr 30, 2026

    @michelroegl-brunner
    michelroegl-brunner
    on Apr 30, 2026
    Member

    Merged with #14121 in ProxmoxVE

  16. michelroegl-brunner
    closed this as completedon Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Migration To ProxmoxVE

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions