# \[solved\] Disable SSH problem

**URL:** <https://forum.gitea.com/t/solved-disable-ssh-problem/897>\
**Category:** Install/Maintain/Configure\
**Created:** [February 1, 2019, 2:24pm UTC](https://forum.gitea.com/t/solved-disable-ssh-problem/897 "2019-02-01T14:24:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![elcs](https://avatars.discourse-cdn.com/v4/letter/e/ac91a4/32.png) [@elcs](https://forum.gitea.com/u/elcs)\
**Post date:** [February 1, 2019, 2:24pm UTC](https://forum.gitea.com/t/solved-disable-ssh-problem/897/1 "2019-02-01T14:24:33Z")

</div>

Hello,

I installed the gitea via docker (in OpenMediaVault) and I have problem with SSH:

- even I have set DISABLE\_SSH to ‘true’, the gitea still tries to bind ssh
- the port reconfiguration does not work - if I change to port to e.g. 3022, it still tries to bind to port 22, but the port 22 I have already assigned by system

The Docker’s log of container is full of following:  
Feb 1 14:17:33 sshd[100]: error: Bind to port 22 on :: failed: Address in use.  
Feb 1 14:17:33 sshd[100]: error: Bind to port 22 on 0.0.0.0 failed: Address in use.  
Feb 1 14:17:33 sshd[100]: fatal: Cannot bind any address.  
Feb 1 14:17:34 sshd[105]: error: Bind to port 22 on :: failed: Address in use.  
Feb 1 14:17:34 sshd[105]: error: Bind to port 22 on 0.0.0.0 failed: Address in use.  
Feb 1 14:17:34 sshd[105]: fatal: Cannot bind any address.  
Feb 1 14:17:35 sshd[110]: error: Bind to port 22 on :: failed: Address in use.  
Feb 1 14:17:35 sshd[110]: error: Bind to port 22 on 0.0.0.0 failed: Address in use.  
Feb 1 14:17:35 sshd[110]: fatal: Cannot bind any address.  
Feb 1 14:17:36 sshd[115]: error: Bind to port 22 on :: failed: Address in use.  
Feb 1 14:17:36 sshd[115]: error: Bind to port 22 on 0.0.0.0 failed: Address in use.  
Feb 1 14:17:36 sshd[115]: fatal: Cannot bind any address.

Please, how it is possible to really disable the SSH, which gitea tries to start?

Thank you

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [February 2, 2019, 1:40pm UTC](https://forum.gitea.com/t/solved-disable-ssh-problem/897/2 "2019-02-02T13:40:47Z")

</div>

Did you add a -p on docker command line?

---

<div class="post-metadata">

**Author:** ![elcs](https://avatars.discourse-cdn.com/v4/letter/e/ac91a4/32.png) [@elcs](https://forum.gitea.com/u/elcs)\
**Post date:** [February 4, 2019, 7:44am UTC](https://forum.gitea.com/t/solved-disable-ssh-problem/897/3 "2019-02-04T07:44:30Z")

</div>

What is the function of -p argument?  
If the argument, passed to docker is simply passed to hosted application, I can see here [https://docs.gitea.io/en-us/command-line/](https://docs.gitea.io/en-us/command-line/), that the -p (–port) changes the default port 3000, but this is the port of http.

---

<div class="post-metadata">

**Author:** ![elcs](https://avatars.discourse-cdn.com/v4/letter/e/ac91a4/32.png) [@elcs](https://forum.gitea.com/u/elcs)\
**Post date:** [February 6, 2019, 2:45pm UTC](https://forum.gitea.com/t/solved-disable-ssh-problem/897/4 "2019-02-06T14:45:46Z")

</div>

Hello, I found it - the problem was setup the network mode to ‘host’. When I reconfigured it to ‘bridge’ with properly port forward (using -p arg), the Gitea works fine using both 3000 and 22 ports.

---

<div class="post-metadata">

**Author:** ![techknowlogick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/techknowlogick/32/4706_2.png) [@techknowlogick](https://forum.gitea.com/u/techknowlogick)\
**Post date:** [February 14, 2019, 9:33pm UTC](https://forum.gitea.com/t/solved-disable-ssh-problem/897/5 "2019-02-14T21:33:24Z")

</div>

Closed on February 14, 2019, 9:33pm UTC


