Dan

And Fedora currently had version 1.9A in it's repo..

I did a quick test with the following equipment:

• host: fedora. starts the wemux server by invoking tmuxinator.
• user: ssh from another computer into a user account of the Fedora host.

On host (server), I did the following 5 commands as a test:

• mux MYSESSION
  
  The session starts well. I check from remote computer by ssh into a user account, and get "No wemux server to attach to on 'wemux'".message

• ctrl-b, d
  To detach and go back to prompt

• ls -la /tmp
  To check permissions on wemux-wemux. Permissions are 660.

• chmod 1777 /tmp/wemux-wemux
  
  Change according to README

• ls -la /tmp # to double-check permissions on wemux-wemux

So it appears to be a problem with the permissions of the socket. That doesn't explain the first problem I had with renaming the wemux default host. Obviously the socket name changes but I couldn't get it to start in the first place by changing that. I don't have the time to check it out. It's what the session name is in tmuxinator that is important. There is no need to change the default server name in wemux config if using through tmuxinator anyways.

I'm out of time. I just wanted to do a quick test as I am trying it out now...

Thanks alot for this tip!

athal7,

I had the same problem and solved it. The message I was getting was "No wemux server to attach to on 'wemux'".

1. the first problem I seemed to have was when changing the default name in the wemux config. I re-commented that line so the only line I had effectively was for the allowed host. Then my host could run a server.
2. the second problem seems to be that the socket directory has the wrong group permissions. According to the readme:

"Host Commands
wemux start
Use wemux start to start a wemux server, chmod /tmp/wemux-wemux to 1777 so that other users may connect to it, and attach to it. If a wemux server already exists, it will attach to it instead."
https://github.com/zolrath/wemux/blob/master/README.md

Mine had the group permission set to 0. If I chmod that directory as instructed, and call "mux SESSIONNAME" as usual, it works.