# Webserver TCP port

**URL:** <https://forums.digi.com/t/webserver-tcp-port/17126>\
**Category:** Digi TransPort WR (Series)\
**Tags:** wr44, webserver\
**Created:** [July 25, 2016, 2:53am UTC](https://forums.digi.com/t/webserver-tcp-port/17126 "2016-07-25T02:53:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jserink](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@jserink](https://forums.digi.com/u/jserink)\
**Post date:** [July 25, 2016, 2:53am UTC](https://forums.digi.com/t/webserver-tcp-port/17126/1 "2016-07-25T02:53:57Z")

</div>

Can the TCP port for the default web server in the Digi Transport be reassigned to say port 8080?

---

<div class="post-metadata">

**Author:** ![NicholasWilson](https://avatars.discourse-cdn.com/v4/letter/n/c77e96/32.png) [@NicholasWilson](https://forums.digi.com/u/NicholasWilson)\
**Post date:** [July 25, 2016, 3:19am UTC](https://forums.digi.com/t/webserver-tcp-port/17126/2 "2016-07-25T03:19:27Z")

</div>

No, but you can use the firewall to swap it over.

EG, forward requests on port 8080 to port 80 and any requests for port 80 to whatever device you want.

In your example for port 8080 the Digi is actually listening on 8080 if you have HTTP enabled.

port 8443 for https and port 8022 for SSH are listening if you enable the appropriate service. These numbers can not be changed only blocked or redirected in the firewall.

---

<div class="post-metadata">

**Author:** ![jserink](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@jserink](https://forums.digi.com/u/jserink)\
**Post date:** [July 25, 2016, 3:38am UTC](https://forums.digi.com/t/webserver-tcp-port/17126/3 "2016-07-25T03:38:02Z")

</div>

ok, I have found a work around.  
I enabled the HTTPS server and turned off the HTTP server. In Connections-\>IP Connections the socket waiting on TCP 80 has disappeared. So this will work.

Cheers,  
John

---

<div class="post-metadata">

**Author:** ![James.Wilson](https://avatars.discourse-cdn.com/v4/letter/j/53a042/32.png) [@James.Wilson](https://forums.digi.com/u/James.Wilson)\
**Post date:** [July 25, 2016, 4:39am UTC](https://forums.digi.com/t/webserver-tcp-port/17126/4 "2016-07-25T04:39:03Z")

</div>

Hi

you if you want to use port 80 for port forwarding or to block it you could use the firewall to protect or forward the port

regards

---

<div class="post-metadata">

**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\
**Post date:** [July 29, 2016, 4:18pm UTC](https://forums.digi.com/t/webserver-tcp-port/17126/5 "2016-07-29T16:18:22Z")

</div>

Just to clarify, with the current Transport firmware, the TransPort listens on both ports 80 and 8080 by default. If the firmware your unit’s running is “older”, then it may behave differently with respect the HTTP port(s).