Package Details: unified-remote-server 3.6.0.745-5

Git Clone URL: https://aur.archlinux.org/unified-remote-server.git (read-only, click to copy)
Package Base: unified-remote-server
Description: Unified Remote Server
Upstream URL: http://www.unifiedremote.com/
Keywords: remote
Licenses: Freeware
Submitter: Peace4all
Maintainer: blackhole
Last Packager: blackhole
Votes: 46
Popularity: 0.99
First Submitted: 2014-04-30 19:18
Last Updated: 2020-05-09 23:43

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 11 Next › Last »

Jonhoo commented on 2014-10-13 16:56

@fahq613: The trouble with that (as pointed out by others below) is that it makes the server run as root which is neither necessary nor secure..

fahq613 commented on 2014-10-13 16:48

Here is my proposed Systemd startup file so that you can enable the server to startup on boot. I've uploaded it to pastebin as well as included it in this post. It works for me so i figured id share to try and help somebody out http://pastebin.com/raw.php?i=i9pr02cQ

/etc/systemd/system/urserver.service
______________________________________

[Unit]
Description=Start Unified Remote service
After=network.target

[Service]
Type=forking
User=root
ExecStart=/opt/urserver/urserver --daemon --pidfile=/var/run/urserver.pid
PIDFile=/var/run/urserver.pid

[Install]
WantedBy=multi-user.target

Jonhoo commented on 2014-09-30 22:17

Updated the PKGBUILD to specify a versioned target filename for the .deb download. This prevents the file validation from failing if an older version of linux-x64-deb is present.

blackhole commented on 2014-09-29 17:14

I discovered that systemd service was started with /etc/default/urserver as configuration but starting as user it was using /home/user/.urserver (maybe from a previous installation).

I have deleted the .urserver configuration folder in my home directory and now is starting fine.

hybrid commented on 2014-09-29 17:00

Wow quick response!
blackhole, you may want to start $/opt/urserver/urserver from a terminal to see if it gives you any errors. If it starts up normally you can enter "monitor" to monitor what the server is doing. While you're monitoring try to connect with your android device. Maybe that gives you an indication as to what is causing your trouble.
Personally I don't want a server like that to be running all the time, so I manually start and kill it whenever I want to.
But I just tried to run urserver --daemon as a regular user and connected to it with my android device. Worked fine, just as intended.

Peace4all: I like your new .install. Thank you for the quick reply and the package.
Since on my machine urserver works as intended as a user (http://www.unifiedremote.com/guides/linux/command-line tells you to run it as a user) I don't know why it's not working for you. As I suggested blackhole to do: Try running the server from a terminal (not as a daemon) and have it monitor. That will hopefully give you a hint as to why it's not working.
I would really expect some configuration error (like you were using a password or encryption for urserver, you used to start it with -cpath path/to/config and now you're starting it without) rather than something like missing groups or x root/non-root mode.
But again, I can't reproduce your error so I can only guess here. Have the urserver monitor and try to investigate from there.

hybrid commented on 2014-09-29 16:43

Wow quick response!
blackhole, you may want to start $/opt/urserver/urserver from a terminal to see if it gives you any errors. If it starts up normally you can enter "monitor" to monitor what the server is doing. While you're monitoring try to connect with your android device. Maybe that gives you an indication as to what is causing your trouble.
Personally I don't want a server like that to be running all the time, so I manually start and kill it whenever I want to.
But I just tried to run urserver --daemon as a regular user and connected to it with my android device. Worked fine, just as intended.

Leithal commented on 2014-09-29 11:32

Thanks, both methods worked for me.

Leithal commented on 2014-09-29 11:32

Thanks, both methods worked for me.

blackhole commented on 2014-09-29 10:12

Is seems that in my case /opt/urserver/urserver --daemon is not working.
urserver start as user without errors, but the android app cannot connect any more.
Also web interface at http://<your_computer_address>:9510/web is not working:
File Not Found
/web

I have cleaned cache on android app but result is the same.

With systemd service file it was working fine.

Peace4all commented on 2014-09-28 17:09

I updated the package quickly, and removed the systemd file completely, I have suggested to run the server as a daemon and does not require root, start with:
#/opt/urserver/urserver --daemon

There are likely other ways to start.