# How do I disable auto updates? (1.19 breaks Digital Ocean droplet)

**URL:** <https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912>\
**Category:** Install/Maintain/Configure\
**Created:** [March 20, 2023, 11:11pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912 "2023-03-20T23:11:48Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbutterick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mbutterick/32/5183_2.png) [@mbutterick](https://forum.gitea.com/u/mbutterick)\
**Post date:** [March 20, 2023, 11:11pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/1 "2023-03-20T23:11:48Z")

</div>

My Gitea server went down earlier. I could only get it running again by restoring a backup. I realized that the backup has 1.18.5, and after a few minutes it automatically updates to 1.19, which breaks my server.

**I don’t want 1.19! How do I disable the update?**

---

<div class="post-metadata">

**Author:** ![delvh](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/delvh/32/5047_2.png) [@delvh](https://forum.gitea.com/u/delvh)\
**Post date:** [March 20, 2023, 11:15pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/2 "2023-03-20T23:15:42Z")

</div>

The only way this can happen is if you use `docker` with the `latest` tag or similar.  
We strongly recommend using a specific version instead, unless you always want to upgrade as soon as possible.  
However, this is standard Docker behavior that Gitea (thankfully) has no influence over.  
Or how exactly else did you manage to autoupdate your server? 🤨

---

<div class="post-metadata">

**Author:** ![mbutterick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mbutterick/32/5183_2.png) [@mbutterick](https://forum.gitea.com/u/mbutterick)\
**Post date:** [March 20, 2023, 11:22pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/3 "2023-03-20T23:22:18Z")

</div>

I used the [Digital Ocean One-Click droplet](https://marketplace.digitalocean.com/apps/gitea) to set up the server about 8 months ago. But there is no `docker` command at the prompt. How else might I affect that part of the configuration?

---

<div class="post-metadata">

**Author:** ![delvh](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/delvh/32/5047_2.png) [@delvh](https://forum.gitea.com/u/delvh)\
**Post date:** [March 20, 2023, 11:32pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/4 "2023-03-20T23:32:22Z")

</div>

Okay, didn’t know about Digital Ocean.  
Perhaps you should ask them how to disable auto-updates.  
Gitea can’t really do anything here (except not release anything anymore, which is not a viable solution).  
If your provider decides to auto-update on a restart there’s nothing we can do…

---

<div class="post-metadata">

**Author:** ![mbutterick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mbutterick/32/5183_2.png) [@mbutterick](https://forum.gitea.com/u/mbutterick)\
**Post date:** [March 20, 2023, 11:44pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/5 "2023-03-20T23:44:51Z")

</div>

On closer inspection, the Digital Ocean droplet uses `snap` to manage the Gitea installation. I learned that you can revert to the last version like so:

```auto
snap revert gitea

```

And then prevent it from re-updating like so:

```auto
snap refresh --hold

```

So that puts me back on 1.18.5, and the server works again.

---

<div class="post-metadata">

**Author:** ![mbutterick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mbutterick/32/5183_2.png) [@mbutterick](https://forum.gitea.com/u/mbutterick)\
**Post date:** [March 20, 2023, 11:54pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/6 "2023-03-20T23:54:51Z")

</div>

AFAICT the Digital Ocean one-click droplet never set up Gitea to run under a user named `git`, which 1.19 seems to assume is the case. Therefore, it’s possible other DO users may encounter this problem.

---

<div class="post-metadata">

**Author:** ![jolheiser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/jolheiser/32/4807_2.png) [@jolheiser](https://forum.gitea.com/u/jolheiser)\
**Post date:** [March 21, 2023, 12:06am UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/7 "2023-03-21T00:06:57Z")

</div>

Do you happen to have any logs or error messages? `git` is what we _recommend_, but it isn’t required.

---

<div class="post-metadata">

**Author:** ![mbutterick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mbutterick/32/5183_2.png) [@mbutterick](https://forum.gitea.com/u/mbutterick)\
**Post date:** [March 21, 2023, 12:42am UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/8 "2023-03-21T00:42:47Z")

</div>

While I had 1.19 on my server and tried to run `gitea start`, I got this error —

```auto
setting.go:322:loadRunModeFrom() [F] 
Expect user 'git' but current user is: root

```

It seems to arise from [this restriction](https://github.com/go-gitea/gitea/blob/623a539f23ba2a3d051a522d679780aefcf06e6f/modules/setting/setting.go#L286) in the source. I’m sure intentions were good but there may be gentler ways of nudging people away from `root` than bricking the server 😉

---

<div class="post-metadata">

**Author:** ![jolheiser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/jolheiser/32/4807_2.png) [@jolheiser](https://forum.gitea.com/u/jolheiser)\
**Post date:** [March 21, 2023, 12:54am UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/9 "2023-03-21T00:54:33Z")

</div>

That was added back in `1.16.0`, so I’m not sure why it would pop up now.

~~It was listed as a breaking change back then iirc~~ I guess it wasn’t…even though the PR was labeled breaking. I will take a look at that. That version is fairly old, but we may still want to update it for posterity.

wrt the warning, it should (imo) absolutely die early rather than run as the root user and start creating directories, etc on startup

---

<div class="post-metadata">

**Author:** ![advation](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/advation/32/3530_2.png) [@advation](https://forum.gitea.com/u/advation)\
**Post date:** [March 21, 2023, 8:15pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/10 "2023-03-21T20:15:34Z")

</div>

I ran into this as well - I wasn’t able to troubleshoot the droplet instance and had to manually recover my repositories. I’m currently looking into another more stable solution for hosting git repos. Any recommendations?

---

<div class="post-metadata">

**Author:** ![linkp](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/linkp/32/4833_2.png) [@linkp](https://forum.gitea.com/u/linkp)\
**Post date:** [March 22, 2023, 2:09am UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/11 "2023-03-22T02:09:47Z")

</div>

The gitea binary behind a reverse proxy works well.

---

<div class="post-metadata">

**Author:** ![mbutterick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mbutterick/32/5183_2.png) [@mbutterick](https://forum.gitea.com/u/mbutterick)\
**Post date:** [March 23, 2023, 2:34pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/12 "2023-03-23T14:34:16Z")

</div>

Looking at your [comment here,](https://forum.gitea.com/t/gitea-doesnt-start-after-update-to-1-19/6920/2) I wondered if my `RUN_USER` was set incorrectly on my Digital Ocean droplet. But my `app.ini` shows `RUN_USER = git`. Despite this, the 1.19 upgrade still failed with the [error noted above](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/8).

---

<div class="post-metadata">

**Author:** ![jolheiser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/jolheiser/32/4807_2.png) [@jolheiser](https://forum.gitea.com/u/jolheiser)\
**Post date:** [March 23, 2023, 2:43pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/13 "2023-03-23T14:43:27Z")

</div>

Yep, your config seems correct. The problem appears to be that `gitea` is being ran as `root` on the machine, and that’s the part I’m not sure about. I don’t know much about droplets or how the single-click works, but perhaps the problem lies there.

---

<div class="post-metadata">

**Author:** ![mbutterick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/mbutterick/32/5183_2.png) [@mbutterick](https://forum.gitea.com/u/mbutterick)\
**Post date:** [March 25, 2023, 8:53pm UTC](https://forum.gitea.com/t/how-do-i-disable-auto-updates-1-19-breaks-digital-ocean-droplet/6912/14 "2023-03-25T20:53:09Z")

</div>

FWIW [the one-click droplet](https://marketplace.digitalocean.com/apps/gitea) is attributed to the Gitea organization (unofficial droplets say “Digital Ocean”) and says “Supported By: Gitea” (again, other unofficial droplets say Digital Ocean). Which creates the impression, apparently incorrect, that the droplet is an official artifact of the Gitea developers (which is why I and perhaps others relied on it).

[Instructions for converting](https://forum.gitea.com/t/how-to-convert-digital-ocean-snap-droplet-to-binary-installation/6954) droplet to binary installation.
