# Change WebClipper's host and port

**URL:** <https://discourse.joplinapp.org/t/change-webclippers-host-and-port/17029>\
**Category:** Features\
**Tags:** tips-and-tricks, how-to\
**Created:** [29 April 2021 22:39 UTC](https://discourse.joplinapp.org/t/change-webclippers-host-and-port/17029 "2021-04-29T22:39:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![matheusfillipe](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/matheusfillipe/32/8500_2.png) [@matheusfillipe](https://discourse.joplinapp.org/u/matheusfillipe)\
**Post date:** [29 April 2021 22:39 UTC](https://discourse.joplinapp.org/t/change-webclippers-host-and-port/17029/1 "2021-04-29T22:39:20Z")

</div>

I should be a fairly "easy" and needed to be able to configure what host and port webclipper will connect to. I have another machine that is running joplin on the same LAN that I want to use webclipper from. If I could only configure the host ip on it it would supposedly just work.

I tried a workaround thought that caused an unexpected behavior. I ran `socat TCP-LISTEN:41184,fork TCP:10.42.0.218:41184` on the remote machine, where 10.42.0.218 is the machine where joplin is running, i was intending to port foward my 127.0.0.1:41184 to the server in order to make it work. But then, when viewing webclipper it said "searching", which it wasn't before, but firefox suddenly used so much ram that I had to restart the machine.

The machine is a ubuntu 20.04 lts. It has low resources. Maybe that is a bug on the webclipper plugin? Is there another tested way i could port forward it....

---

<div class="post-metadata">

**Author:** ![tessus](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/tessus/32/13_2.png) [@tessus](https://discourse.joplinapp.org/u/tessus)\
**Post date:** [30 April 2021 00:20 UTC](https://discourse.joplinapp.org/t/change-webclippers-host-and-port/17029/2 "2021-04-30T00:20:31Z")

</div>

The webclipper only listens on the loopback interface, thus you have to use a bit of a workaround.

On the machine with the webclipper service do this:

```auto
socat TCP4-LISTEN:2006,fork TCP4:127.0.0.1:41184

```

On your machine with the browser, this:

```auto
socat TCP4-LISTEN:41184,fork TCP4:10.42.0.218:2006 

```

That should do the trick.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/3X/1/c/1c948e33314e232a0927789508474d8624f4270b.png) [@system](https://discourse.joplinapp.org/u/system)\
**Post date:** [29 June 2021 00:20 UTC](https://discourse.joplinapp.org/t/change-webclippers-host-and-port/17029/3 "2021-06-29T00:20:37Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.