# Can't Upgrade from v71a to v73, It's Stuck at v71a

**URL:** <https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172>\
**Category:** Help with Setup/Upgrade\
**Created:** [December 10, 2025, 8:19pm UTC](https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172 "2025-12-10T20:19:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![stn](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/stn/32/1100_2.png) [@stn](https://discourse.mailinabox.email/u/stn)\
**Post date:** [December 10, 2025, 8:19pm UTC](https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172/1 "2025-12-10T20:19:14Z")

</div>

**NOTE** : I have searched for similar topics or problems and nothing aligned so:

I have MIAB **v71a** and when I login via SSH and run `sudo mailinabox` it goes through all the upgrade steps successfully, but when I reboot **AND/OR** run `sudo mailinabox` it again it says I have MIAB **v71a** like so (over-and-over):

```auto
Primary Hostname: hostname.domain.com
Public IP Address: 000.000.000.000
Mail-in-a-Box Version: v71a

```

I can’t get v73 to be listed as my version of my server

`screenfetch` info:

```auto
root@hostname.domain.com
OS: Ubuntu 22.04 jammy
Kernel: x86_64 Linux 5.15.0-163-generic
Uptime: 17m
Packages: 1030
Shell: bash 5.1.16
Disk: 7.3G / 99G
CPU: 2.2GHz
GPU: Red Hat, Inc. Virtio GPU (rev 01)
RAM: 768MiB / 1963MiB

```

- I am not using Tmux in SSH, just SSH like normal (although I tried using Tmux with no difference).

Anyone else have difficulties updating from v71a or similar, or was anyone else stuck like this who knows a workaround?

---

<div class="post-metadata">

**Author:** ![stn](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/stn/32/1100_2.png) [@stn](https://discourse.mailinabox.email/u/stn)\
**Post date:** [December 10, 2025, 8:39pm UTC](https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172/2 "2025-12-10T20:39:18Z")

</div>

Here is what my Status Page says:

```auto
System Status Checks
No reboot is necessary.
Disable New-Version Check
Summary: 90 ✓ OK, 1 ✖ Error, 0 ? Warning
System

✓ All system services are running.
✓ SSH disallows password-based login.
✓ System software is up to date.
✖ A new version of Mail-in-a-Box is available. \
You are running version v71a. The latest version \
is v73. For upgrade instructions, see \
https://mailinabox.email.
...

```

---

<div class="post-metadata">

**Author:** ![andrew](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/andrew/32/1449_2.png) [@andrew](https://discourse.mailinabox.email/u/andrew)\
**Post date:** [December 10, 2025, 10:32pm UTC](https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172/3 "2025-12-10T22:32:51Z")

</div>

What does it say when you try to upgrade?

---

<div class="post-metadata">

**Author:** ![stn](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/stn/32/1100_2.png) [@stn](https://discourse.mailinabox.email/u/stn)\
**Post date:** [December 10, 2025, 11:26pm UTC](https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172/4 "2025-12-10T23:26:04Z")

</div>

I log in with **ssh** and run `sudo mailinabox` or just `mailinabox`. It runs through a normal upgrade which gives me:

```auto
Primary Hostname: subdomain.domain.com
Public IP Address: 000.000.000.000
Mail-in-a-Box Version: v71a

Updating system packages...
Installing system packages...
Initializing system random number generator...
Firewall is active and enabled on system startup
Synchronizing state of fail2ban.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable fail2ban
Installing nsd (DNS server)...
Installing Postfix (SMTP server)...
Installing Dovecot (IMAP server)...
Installing OpenDKIM/OpenDMARC...
Installing SpamAssassin...
Installing Nginx (web server)...
Installing Roundcube (webmail)...
Installing Nextcloud (contacts/calendar)...
Nextcloud is already latest version
Installing Z-Push (Exchange/ActiveSync server)...
Installing Mail-in-a-Box system management daemon...
Installing Munin (system monitoring)...
updated DNS: OpenDKIM configuration

-----------------------------------------------

Your Mail-in-a-Box is running.
Please log in to the control panel for further instructions at:
https://subdomain.domain.com/admin
If you have a DNS problem put the box's IP address in the URL
(https://000.000.000.000/admin) but then check the TLS fingerprint:
RE:AL:YL:ON:GF:IN:GE:RP:RI:NT

```

I get this every time, but yet it never actually upgrades to v73. It always still is stuck as v71a.

If I rerun or reboot then rerun the `sudo mailinabox` it’ll say ‘Mail-in-a-Box Version: v71a’ like above.

---

<div class="post-metadata">

**Author:** ![stn](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/stn/32/1100_2.png) [@stn](https://discourse.mailinabox.email/u/stn)\
**Post date:** [December 11, 2025, 12:25am UTC](https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172/5 "2025-12-11T00:25:05Z")

</div>

OK **Update** and **Note-to-My-Future-Self** :

I guess I misunderstand the purpose of:  
`sudo mailinabox`

as when I used that, it would not upgrade from v71a to v73.

However when I did the original:  
`curl -s https://mailinabox.email/setup.sh | sudo bash `

it finally proceeded to upgrade just fine.

Thanks,  
#solved

“A jack of all trades is a master of none, but oftentimes better than a master of one.”

---

<div class="post-metadata">

**Author:** ![system](https://discourse.mailinabox.email/uploads/default/original/2X/4/4d0933d13c456b7e57f296aa6cc344525b6f0c70.png) [@system](https://discourse.mailinabox.email/u/system)\
**Post date:** [December 18, 2025, 12:25am UTC](https://discourse.mailinabox.email/t/cant-upgrade-from-v71a-to-v73-its-stuck-at-v71a/16172/6 "2025-12-18T00:25:34Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.