localhost:8834: Opening the Nessus Interface
Tenable Nessus serves its web interface at https://localhost:8834 on the machine where it is installed. The address needs https, and the browser warns about Nessus's self-signed certificate, which is expected locally. If nothing loads, the nessusd service is stopped; start it, wait for plugins to compile, then reload.
| Platform | Start | Stop |
|---|---|---|
| Linux (systemd) | sudo systemctl start nessusd | sudo systemctl stop nessusd |
| Windows | net start "Tenable Nessus" | net stop "Tenable Nessus" |
| macOS | sudo launchctl start com.tenablesecurity.nessusd | sudo launchctl stop com.tenablesecurity.nessusd |
Updated
After install and after updates, Nessus spends several minutes compiling its plugins. The page loads during that time but shows an initializing bar, and scans cannot start until it finishes, so patience fixes many 'broken' installs.
Confirm the service is listening
Linux
The ss line shows nessusd on 8834 once it is up.
sudo systemctl start nessusd
sudo systemctl status nessusd
sudo ss -ltnp | grep 8834Scanning your own sites only
Scan only hosts you own or have written permission to test. For a site that We.Inc hosts, the servers are ours, so ask support rather than pointing a scanner at them.
How it works
- Start the Nessus service with the command for your system.
- Open https://localhost:8834, including the https prefix.
- Accept the certificate warning for this local page.
- Enter the activation code and create the admin account when prompted.
Tips
- http://localhost:8834 without the s fails; the service only speaks TLS.
- From another computer use https://<scanner-ip>:8834 and allow the port in the scanner's firewall.
- Replacing the self-signed certificate with one from your own certificate authority removes the warning for everyone on the network.
Frequently asked questions
Why does https://localhost:8834 not load?
The nessusd service is not running, or it is still starting. Start the service, wait a minute, and check that something listens on 8834 with netstat or lsof.
Is the certificate warning on 8834 dangerous?
On your own machine it is expected, because Nessus creates a self-signed certificate at install. On a shared network, install a trusted certificate instead of teaching people to click through warnings.
Why is Nessus stuck on initializing?
It is compiling plugins, which can take a long time on a small machine. If it never finishes, check disk space and the logs in the Nessus install folder.
Can I change the Nessus port?
Yes. Use nessuscli fix --set xmlrpc_listen_port=<port> and restart the service. Then open the interface on the new port.
Related: Your connection is not private, localhost:8443, localhost:9090, What is localhost.
Start for free or see all free tools. We.Inc is free to start, with no card needed. AI building is on paid plans from $20 a month.
More in Guides
- localhost:8888: Jupyter Tokens and MAMP
- localhost:9000: Which Program Is It?
- localhost:9090: Prometheus or Cockpit
- localhost Refused to Connect: Find the Cause in Minutes
- Location Pages SEO: Real Pages for Real Places
- Logo Size for a Website: Every Size You Need
- How to Make a Website with HTML and CSS
- Markdown Cheat Sheet
Product
Who It's For
- For Agencies
- For Freelancers
- For Hosting Providers
- For SaaS Platforms
- For Startups
- For Financial Services
- For Healthcare
Features
Resources
- Blog
- Help Center
- Free Business Tools
- Free UI Components
- Website Templates
- Template Collections
- Website Examples
- Guides
- Comparisons
- Alternatives
- Best Lists
- Reviews
- Pricing Guides
- Use Cases
- Glossary & Guides
- Integrations
- Developers
- Benchmark
- Windows App