# Upgrade to v61 backup error

**URL:** <https://discourse.mailinabox.email/t/upgrade-to-v61-backup-error/10050>\
**Category:** uncategorized\
**Created:** [January 23, 2023, 4:27am UTC](https://discourse.mailinabox.email/t/upgrade-to-v61-backup-error/10050 "2023-01-23T04:27:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DrMartin](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/drmartin/32/2755_2.png) [@DrMartin](https://discourse.mailinabox.email/u/DrMartin)\
**Post date:** [January 23, 2023, 4:27am UTC](https://discourse.mailinabox.email/t/upgrade-to-v61-backup-error/10050/1 "2023-01-23T04:27:03Z")

</div>

I use the standard port (22) for rsync but got this error on my backup after upgrade to 61 from 60.1:

```auto
Bad port 'None'
. rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
. rsync error: error in rsync protocol data stream (code 12) at io.c(228) [Receiver=3.2.3]

```

Adding :22 to the hostname fixed the problem.

---

<div class="post-metadata">

**Author:** ![informatom](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/informatom/32/1580_2.png) [@informatom](https://discourse.mailinabox.email/u/informatom)\
**Post date:** [January 23, 2023, 8:11am UTC](https://discourse.mailinabox.email/t/upgrade-to-v61-backup-error/10050/2 "2023-01-23T08:11:47Z")

</div>

I can confirm the error, manual run of ‘sudo management/backup.py’ works fine.  
The backup status page [https://box.mittenin.at/admin](https://box.mittenin.at/admin) can no longer be reached: Either ‘Loading…’ forever or ‘something went wrong’ (so I struggle to add the 22 port).

---

<div class="post-metadata">

**Author:** ![Xaxou](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/x/45deac/32.png) [@Xaxou](https://discourse.mailinabox.email/u/Xaxou)\
**Post date:** [January 26, 2023, 6:23pm UTC](https://discourse.mailinabox.email/t/upgrade-to-v61-backup-error/10050/4 "2023-01-26T18:23:18Z")

</div>

I can confirm this error too.  
Thanks @DrMartin : it works when writing the hostname as ipv4:22 (under System / Backup Status)