access maas 5240 port deny without ipv6
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS documentation |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Describe the bug:
MAAS dashbord/gui (http://
Steps to reproduce:
ubuntu@maas1:~$ sudo snap services maas
Service Startup Current Notes
maas.pebble enabled active -
ubuntu@maas1:~$ !curl
curl http://
<html>
<head><title>301 Moved Permanently<
<body>
<center><h1>301 Moved Permanently<
<hr><center>
</body>
</html>
ubuntu@maas1:~$ sudo vi /etc/default/grub
ubuntu@maas1:~$ grep GRUB_CMDLINE_LINUX /etc/default/grub
GRUB_CMDLINE_
GRUB_CMDLINE_
ubuntu@maas1:~$ sudo update-grub
ubuntu@maas1:~$ sudo reboot
ubuntu@maas1:~$ ip a |grep inet6
ubuntu@maas1:~$ sudo snap services maas
Service Startup Current Notes
maas.pebble enabled active -
ubuntu@maas1:~$ curl http://
curl http://
curl: (7) Failed to connect to 127.0.0.1 port 5240 after 0 ms: Couldn't connect to server
ubuntu@maas1:~$
Expected behavior (what should have happened?):
It should also working too with ipv4 only.
Actual behavior (what actually happened?):
5240 listend failed without ipv6
MAAS version and installation type (deb, snap):
maas: 3.6.0-17541-
MAAS setup (HA, single node, multiple regions/racks):
Host OS distro and version:
ubuntu 24.04
Additional context:
temp disable ipv6 like:
net.ipv6.
net.ipv6.
net.ipv6.
It can't reproduce this issue.

IPv6 is currently required and it should be documented in the installation requirements. Moving to a maas-doc bug so that we keep track