You can set the option live-config.noautologin in a configuration file.
Configuration files can be placed either in the root filesystem itself (/etc/live/config.conf and/or /etc/live/config/*), or on the live media (live/config.conf and/or live/config/*). If both places are used for a certain option, the ones from the live media take precedence over the ...
Solved it on my own, the problem was that if you are not using the default server location, try looking at this page: https://wasabi-support.zendesk.com/hc/en-us/articles/360015106031-What-are-the-service-URLs-for-Wasabi-s-different-regions-
replace the url with your server's location
Fixed my problem!
When your interfaces file has something like address 192.0.2.1/24, that specifies the address and the "netmask" (in the form of the /n network prefix length) all in one go.
Previously, the interfaces file would have had separate address 192.0.2.1 and netmask 255.255.255.0 entries in that same situation. It's simply a modernization to consistently ...
In simple terms, 10.0.2.1/32 means that you set 10.0.2.1 on your network interface but you are alone, the whole network is just your IP.
On the other hand, setting 10.0.2.1/24 means that your IP is 10.0.2.1 and the IP range 10.0.2.0-10.0.2.255 is a known, familiar, reachable block of IPs; no gateway (that is, another network device) needed to reach it.