# Solved: OH 4.0.2 Jetty failed to start

**URL:** <https://community.openhab.org/t/solved-oh-4-0-2-jetty-failed-to-start/148863>\
**Category:** Migration\
**Created:** [August 19, 2023, 9:09am UTC](https://community.openhab.org/t/solved-oh-4-0-2-jetty-failed-to-start/148863 "2023-08-19T09:09:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![s0170071](https://community.openhab.org/user_avatar/community.openhab.org/s0170071/32/20561_2.png) [@s0170071](https://community.openhab.org/u/s0170071)\
**Post date:** [August 19, 2023, 9:09am UTC](https://community.openhab.org/t/solved-oh-4-0-2-jetty-failed-to-start/148863/1 "2023-08-19T09:09:20Z")

</div>

I am upgrading from OH 3.4.3 to OH 4.0.2 in a docker environment. As of 4.0.2 I get a Jetty error message that is:  
`2023-08-19 09:22:13.907 [ERROR] [j.pax.web.service.internal.Activator] - Unable to start Pax Web server: Failed to bind to /0.0.0.0:8443`

The switching back to 3.4.3 - the error is gone.

Long story short: I had a code-server container running on that same port.  
Since OH4.0.2 this port is required by OH itself- no idea why.  
Anyway, I moved code-server over to port 8444 which solved the issue for me.

---

<div class="post-metadata">

**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\
**Post date:** [August 19, 2023, 10:06pm UTC](https://community.openhab.org/t/solved-oh-4-0-2-jetty-failed-to-start/148863/2 "2023-08-19T22:06:46Z")

</div>

> [@s0170071](#):
>
> Since OH4.0.2 this port is required by OH itself- no idea why.

OH has _always_ required port 8443. That’s OH’s https port.