# \[Feature Request\] Multiple clients/instances

**URL:** <https://forums.plex.tv/t/feature-request-multiple-clients-instances/24147>\
**Category:** Dev/API Corner\
**Tags:** other-dev\
**Created:** [November 29, 2012, 10:34pm UTC](https://forums.plex.tv/t/feature-request-multiple-clients-instances/24147 "2012-11-29T22:34:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fabje](https://avatars.discourse-cdn.com/v4/letter/f/d07c76/32.png) [@fabje](https://forums.plex.tv/u/fabje)\
**Post date:** [November 29, 2012, 10:34pm UTC](https://forums.plex.tv/t/feature-request-multiple-clients-instances/24147/1 "2012-11-29T22:34:43Z")

</div>

First a big thank you for creating this beautiful piece of software. I’ve used Plex on my Samsung SmartTV for about half a year now and I still love it.  
  
  
  
However I ran into a bit of a problem since we have a second Samsung SmartTV in the house. I have a central Linux file server on which I run the Plex Media Server.  
  
Watching from multiple clients creates a big mess in the “watched/unwatched” status.  
  
I would love to see this problem sorted out and I would like to purpose a few possible solutions:

1. The ideal solution would be Plex to register per client what has been watched an what not. but I can see this requires a lot of work or might interfere with the idea behind Plex.  
  
  
2. An alternative would be to be able to set the IP address/interface the server should bind to.  
  
With this and a bridged interface it would be possible to create multiple instances of the server (setting the their own library/metadata directory is already possible I believe) allowing me to run a separate server for each client.  
  
If this feature gets implemented I’m willing to provide a tutorial how to set this up.  
  
This also allows some more security for severs with multiple Ethernet interfaces.  
  
  
  
I would love to hear other opinions about this.  
  
Thank you!

---

<div class="post-metadata">

**Author:** ![CoolBlue81](https://avatars.discourse-cdn.com/v4/letter/c/8e7dd6/32.png) [@CoolBlue81](https://forums.plex.tv/u/CoolBlue81)\
**Post date:** [December 17, 2012, 9:15pm UTC](https://forums.plex.tv/t/feature-request-multiple-clients-instances/24147/2 "2012-12-17T21:15:03Z")

</div>

+1   
  
multiseat shoud be full integrated in the plex core.

---

<div class="post-metadata">

**Author:** ![Haplo](https://avatars.discourse-cdn.com/v4/letter/h/ed655f/32.png) [@Haplo](https://forums.plex.tv/u/Haplo)\
**Post date:** [January 19, 2013, 4:33am UTC](https://forums.plex.tv/t/feature-request-multiple-clients-instances/24147/3 "2013-01-19T04:33:30Z")

</div>

Bump. Is there any workarounds available?  
  
  
  
Edit: Binding to Mac Address would be better to bind to because there is no chance of it being dynamic.

---

<div class="post-metadata">

**Author:** ![ancarius](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@ancarius](https://forums.plex.tv/u/ancarius)\
**Post date:** [January 19, 2013, 1:17pm UTC](https://forums.plex.tv/t/feature-request-multiple-clients-instances/24147/4 "2013-01-19T13:17:40Z")

</div>

+1  
  
  
  
This is something I haven’t seen on any client yet and it would really be nice to have a per client watched list.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [December 20, 2019, 10:29pm UTC](https://forums.plex.tv/t/feature-request-multiple-clients-instances/24147/5 "2019-12-20T22:29:46Z")

</div>

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