Cannot access web interface via port 3000

Grafana Installation
1
  • What Grafana version and what operating system are you using?
    Grafana version:
Version 11.2.0 (commit: c57667e4481563f5e6cf945b03bc0626caa4dbeb, branch: HEAD)

I am running Grafana OSS on Ubuntu Virtual machine:

Ubuntu 24.04.1 LTS
  • What are you trying to achieve?

I am trying to setup Grafana on my Ubuntu Virtual machine

  • How are you trying to achieve it?

I have followed installation steps to install and setup the Grafana on Ubuntu

  • What happened?

Everything seemed fine during the installation, however, I cannot seem to access the webserver on port 3000. My virtual machine IP address is: 10.51.5.1. I am trying to reach:
http://10.51.5.1:3000 and https://10.51.5.1:3000 but it is not reachable.

I have tried to run the sudo systemctl status grafana-server command and got the following:

lukas.petrikas@ems-isp:/var/log/grafana$ sudo systemctl status grafana-server
[sudo] password for lukas.petrikas:
Sorry, try again.
[sudo] password for lukas.petrikas:
● grafana-server.service - Grafana instance
     Loaded: loaded (/usr/lib/systemd/system/grafana-server.service; disabled; preset: enabled)
     Active: active (running) since Mon 2024-09-02 09:34:15 EEST; 28min ago
       Docs: http://docs.grafana.org
   Main PID: 1646 (grafana)
      Tasks: 10 (limit: 4504)
     Memory: 40.6M (peak: 51.0M)
        CPU: 2.815s
     CGroup: /system.slice/grafana-server.service
             └─1646 /usr/share/grafana/bin/grafana server --config=/etc/grafana/grafana.ini --pidfile=/run/grafana/grafana-server.pid --packaging=deb cfg:default.paths.logs=/var/log/grafana cfg:default.paths.>
Sep 02 09:34:15 ems-isp grafana[1646]: logger=ticker t=2024-09-02T09:34:15.909377553+03:00 level=info msg=starting first_tick=2024-09-02T09:34:20+03:00
Sep 02 09:34:16 ems-isp grafana[1646]: logger=plugins.update.checker t=2024-09-02T09:34:16.005180051+03:00 level=info msg="Update check succeeded" duration=96.791101ms
Sep 02 09:34:16 ems-isp grafana[1646]: logger=grafana.update.checker t=2024-09-02T09:34:16.020277398+03:00 level=info msg="Update check succeeded" duration=112.550851ms
Sep 02 09:34:16 ems-isp grafana[1646]: logger=grafana-apiserver t=2024-09-02T09:34:16.758024396+03:00 level=info msg="Adding GroupVersion playlist.grafana.app v0alpha1 to ResourceManager"
Sep 02 09:34:16 ems-isp grafana[1646]: logger=grafana-apiserver t=2024-09-02T09:34:16.7590943+03:00 level=info msg="Adding GroupVersion featuretoggle.grafana.app v0alpha1 to ResourceManager"
Sep 02 09:35:19 ems-isp grafana[1646]: logger=infra.usagestats t=2024-09-02T09:35:19.914946078+03:00 level=info msg="Usage stats are ready to report"
Sep 02 09:44:15 ems-isp grafana[1646]: logger=cleanup t=2024-09-02T09:44:15.911994345+03:00 level=info msg="Completed cleanup jobs" duration=4.636011ms
Sep 02 09:44:16 ems-isp grafana[1646]: logger=plugins.update.checker t=2024-09-02T09:44:16.06817482+03:00 level=info msg="Update check succeeded" duration=61.790048ms
Sep 02 09:54:15 ems-isp grafana[1646]: logger=cleanup t=2024-09-02T09:54:15.911303902+03:00 level=info msg="Completed cleanup jobs" duration=4.20631ms
Sep 02 09:54:16 ems-isp grafana[1646]: logger=plugins.update.checker t=2024-09-02T09:54:16.067990167+03:00 level=info msg="Update check succeeded" duration=61.630344ms

One strange thing that I have noticed is that it says :

Loaded: loaded (/usr/lib/systemd/system/grafana-server.service; disabled; preset: enabled)

Why does it say that grafana-server.service is disabled? Does it have to do anything with the issue that I am having?

I have also tried to reach the localhost:3000 via the virtual machine itself using wget and it seems to work fine:


lukas.petrikas@ems-isp:/tmp$ wget localhost:3000
--2024-09-02 10:05:10--  http://localhost:3000/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:3000... connected.
HTTP request sent, awaiting response... 302 Found
Location: /login [following]
--2024-09-02 10:05:10--  http://localhost:3000/login
Reusing existing connection to localhost:3000.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

index.html                                               [ <=>                                                                                                                ]  37.76K  --.-KB/s    in 0.001s

2024-09-02 10:05:10 (31.9 MB/s) - ‘index.html’ saved [38671]
  • What did you expect to happen?

Being able to reach the web interface on port 3000 on other machines

  • Can you copy/paste the configuration(s) that you are having problems with?

Since I am using fresh install, all configurations are default

  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.

I have tried to look at grafna logs at /var/logs/grafana/grafana.log ant noticed some errors with “Failed to load external plugins” . Does it have to do anything with the issue I am having?

image
image1623×237 13.6 KB

  • Did you follow any online instructions? If so, what is the URL?
https://grafana.com/docs/grafana/latest/setup-grafana/installation/debian/

I would really appreciate if someone could share their insights on what could have gone wrong. What are the next steps and what should I test?

2

Hey @petrikaslukas

No need yo worry about that: it’s only about the Grafana service starting when your VM start (enabled) or not (disabled). If you want it to start with your VM:

systemctl enable grafana-server

To make some test:

  • Can you run systemctl restart grafana-server, and check if that resolve anything?
  • Can you make sure an apache service is running on your grafana VM? Then wget the IP of your grafana VM on a remote machine wget http://your_IP (without any port).
  • After enabling your instance (if you do), you can also try to reboot your VM.
  • Can you check that in your grafna.ini the plugins path is an existing one?
[path]
plugin = /var/lib/grafana/plugins

Or something like that

3

It turned out to be issue form the IT Administrators side. Since I am running this on company server, they had all ports disabled by default. They had to allow traffic through port 3000.

1 Like