Smokeping bug

RouterOS Containers
1

When generating a graph for a custom timeframe, the form action links to "http://localhost/.." instead of the actual host and port combination that's being used. Is there a setting to correct this or a way to get it to use a relative path instead?

2

Hi,

Could you give more details please?
We do not know what, where from and how you prepare that graph.

3

Just by clicking on any of the graphs until you get the option for a custom timeframe. For instance:

ScreenClip
ScreenClip1024×579 36.6 KB

If I click on the "Generate!" button in the screenshot, it'll go the the above mentioned localhost url.

4

So could you explain how the problem is connected with Mikrotik as it seems to be a Smokeping problem.
Shouldn't you ask on Smokeping forum?

5

The problem is connected with Mikrotik because it's running on my Mikrotik device, which was set up using the app config feature in it, and I figured perhaps one of the settings in there is misconfigured or missing for the proper url to be used.

6

Ok, since I had to look into this myself:

This is a known issue at linuxserver, the container that's being used:

@MattKobayashi there submitted a PR to the upstream Smokeping folks, and it was merged on 2/19/2026.

Unfortunately, the upstream Smokeping at:

Had its last release, version 2.9.0 on 2/19/2025, a full year before.

So, everyone's just waiting for a new release of SmokePing.

7

So it is a container inside a MT device running as Smokeping is not a MT solution?
If yes, then how SK gets data from MT device?
What MT is responsible for?
How MT could set any data inside a container?

What "app feature" was used to configure MT devoice or maybe a SK itself?

8

No need to answer questions then

9

ScreenClip
ScreenClip157×675 67.2 KB

This app feature, in Winbox, which is also present in the text config under /app/config.

10

OK, just there was no container context mentioned for Smokeping so it was hard to guess.

11

But you normally don't submit bug reports to Canonical Ltd. when Firefox fails to render some webpage, although it comes preinstalled on desktop Ubuntu?

12

Some people probably do that as well.

13

Are we not in the RouterOS Containers forum?

14

If Firefox is unable to render a webpage repeatedly with a clear pattern to it that might suggest a misconfiguration, I might report that to Canonical.

Up until I looked into this myself, getting Smokeping working was merely clicking Enable in the app config section for that entry. So someone at Mikrotik went through to figure out what container to use, what environment settings to use, etc. So is it unreasonable to think that perhaps that person might be aware of other settings that may be the cause of that form action url being incorrect?

15

Yes, we are but there was no mention that your installation is done with container in Mikrotik

So many posts is placed in inappropriate sections that please forigive for asking for a bit longer context explanation type:
"I have installed Smokeping container in MT model XYZ but when .... the rest of your post ... maybe a little bit extended"

The original post looks more as targeted to Smokeping community than to Mikrotik container specialists.

16

Apologies then for posting concisely in the correct place.