search

MaterialFoundry / MaterialDeck

41 stars 20 forks source link

Create secured websocket version of Material Server, unsecured doesn't work in some situations #60

Open CDeenen opened 3 years ago

madebyhilmi commented 2 years ago

Hey is there any progress on this?

CDeenen commented 2 years ago

Hi, there's no progress on this because it isn't an issue for the vast majority of users. I'm only aware of 1 person who had a very niche setup for whom it didn't work. If you run Material Server on your local machine and set the Material Server Address in the module settings to 'localhost:3001' it should work.

RinVindor commented 2 years ago

I'm going to assume this hasn't changed in terms of being addressed? I host my games via Forge and being able to use my Stream Deck again would be great, I've missed using it since I moved to Forge.

CDeenen commented 2 years ago

I'm going to assume this hasn't changed in terms of being addressed? I host my games via Forge and being able to use my Stream Deck again would be great, I've missed using it since I moved to Forge.

For the Forge it shouldn't be necessary for Material Server to be secured. If it can't connect, there probably is something else going wrong. Please make sure of the following:

  1. Material Server is running on the same computer as the one you're accessing Foundry from, and the Stream Deck is connected to that same computer
  2. You're running Foundry v8 or v9
  3. You're on the latest version of Material Deck for both the module and Stream Deck plugin (both v1.4.10)
  4. In the module settings, 'Enable Module' is ticked
  5. In the module settings, 'Material Server Address' is set to 'localhost:3001'. Do not replace 'localhost' with an IP address, since that will not work for secured Foundry servers.

While there is a valid reason for wanting a secured version of Material Server, this is only necessary for very niche applications (and even then there might be workarounds).