Error: The server connection failed with the error "Bad Gateway"

Users
,
1

I was able to reach the ui until I changed network and put it in its own net without an external DHCP.
Now I get Error: The server connection failed with the error "Bad Gateway".
Can’t find out why.
Any help here?
What kind of logs do I have to look at? (there are tonns)

2

Hi @novski

Which version of MAAS do you have? Is it snap or deb install?

3

I have snap 3.3/stable snap info maas says exactly: installed: 3.3.2-13177-g.a73a6e2bd.

4

I am a new bee.
Could it be the settings which enables DHCP?
How to enable MAAS-managed DHCP

5

How can I check the status?
I only see the CLI Command for setting the DHCP with this link.
And I don’t know my $PROFILE, default VLAN $VLAN_TAG and $PRIMARY_RACK_CONTROLLER Name in

maas $PROFILE vlan update $FABRIC_ID $VLAN_TAG dhcp_on=True \
primary_rack=$PRIMARY_RACK_CONTROLLER

:grin:

6

by chance tried an update to 3.3.4 but that failed with:

  File "/snap/maas/28521/usr/lib/python3/dist-packages/psycopg2/__init__.py", line 122, in connect
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: connection to server at "192.168.178.200", port 5432 failed: No route to host
	Is the server running on that host and accepting TCP/IP connections?

192.168.178.200 is the old IP.
I changed the IP of the device with netplan to 192.168.0.2 a few days ago, before the “bad gateway” came. How do I tell maas it’s new IP address?

7

I already teard down and ran in to other errors and while googleing those i found what might have been the right answer to this question:
change IP config by:
sudo maas config --maas-url=http://1.2.3.4:5240/MAAS

8

@novski, did your command immediately above solve the problem?

9

No. I wasn‘t able to test it, as i had allready teard it down.
Just left that note for future.

10