Https service missing in vyos 1.2.0


I’m using VyOS 1.2.0-rolling+201904120337 and I want to activate web-gui.
I infer this could be done by set service https command, but I’ve seen there’s no option “https” when autocompleting and, of course, it doesn’t work. Has this feature gone?


I’ve seen there is a monitor https command but it throws an error: “tail: unrecognized file system type 0x794c7630 for ‘/var/log/messages’. please report this to reverting to polling”


There is no web gui in VyOS


And this? (


legacy, and will be removed


Oooh, it’s a pity. VyOs could play then in the same league than pfSense, Untangle or the like and maybe it would be more popular.
Would you consider, at least, taking a look at Cockpit? (
Thanks a lot!!


@q2dg Regarding the WebUI vs CLI: initially I’ve used pfSense, and it all worked fine for very simple deployments; however as soon as I entered the realm of complex setups (even starting from multiple similar rules, and certainly with complex configuration scenarios) the following issues started popping up – in order of importance:

  • “click madness” – I needed to define almost the same firewall rule multiple times, but with different parameters (and I couldn’t use lists), it drove me mad… in VyOS I just edit the commands in an text editor, copy-paste and find-and-replace (or even write a small script to generate them);
  • “who changed what, when?” – i.e. diff (or in VyOS compare saved), namely sometimes I wanted to see what I’ve changed last week and I had no way to do so… (granted pfSense does have XML-based configuration files, but when saving them they are not deterministic, namely some interfaces would change order, etc.)
  • “my configuration at a glance” – sometimes I needed to visually compare various firewall rules, however the pfSense “table” wouldn’t show all details, therefore I had to resort to actually open each one, or SSH and issue firewall commands;
  • “misfortune struck and I’m in the server room without my laptop” (or locked out of my administrative VLAN) – many times I was in the situation of being in the “server room” and needing to quickly configure something on my pfSense router, although I had just logged-in on its console, I wasn’t able to do anything because pfSense requires a browser, which it doesn’t provide; :slight_smile:

Another example MikroTik routers: I have a couple of the small hAC routers, which have both CLI and a very good WebUI (in fact sometimes better than pfSense’s, and certainly the best WebUI I’ve seen in any “enterprise” product). I use the WebUI only for simple changes, for any serious configuration I resort to the CLI. (For the same reasons as for pfSense.)

Therefore although there are rough edges to the VyOS configuration language, and certainly sometimes it is more verbose than needed, I would say it has a large advantage over pfSense (and other products) exactly for this reason.

The conclusion (and suggestion): learn to use the CLI, although it has a steep learning curve, and sometimes it is hard to “discover”, it is invaluable both as a learning tool and in case of emergency.

In fact, does anyone know of other open-source software-based routers that have a CLI configuration environment? (I don’t know of one.)


VyOS doesn’t need to play in a league with pfSense - it’s playing in its own league :wink:

There is not much to add, what @ciprian.craciun wrote. +1


Thanks a lot for explain so well this topic.