SiriProxy
SiriProxy copied to clipboard
plamoni
Gencerts not working correctly on new release?
I may be doing this incorrectly, but when I start siriproxy I get an error about 'block in start_tls". It looks like siriproxy is looking for the certs in /root/, but I thought siriproxy should be installed in the non-root-user home directory.
Is this working properly? If so, is there a work around for it? Thanks in advance. Output below:
rvmsudo siriproxy server -d 192.168.2.26 -u pi -L 192.168.2.26 WARN: Unresolved specs during Gem::Specification.reset: rake (>= 0) WARN: Clearing out unresolved specs. Please report a bug if this causes problems. [Notice - Configuration] ==================== Important Configuration Notice ========================== [Notice - Configuration] '/root/.siriproxy/config.yml' not found. Using '/home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/config.example.yml' [Notice - Configuration] [Notice - Configuration] Remove this message by copying '/home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/config.example.yml' into '~/.siriproxy/' [Notice - Configuration] ============================================================================== [Info - Configuration] Loading plugins -- If any fail to load, run siriproxy bundle (not bundle install) to resolve. [Info - Server] Starting SiriProxy on 192.168.2.26:443... [Info - Server] DNS server is not running yet, waiting 1 second... [Info - Server] DNS Server started, tainting 'guzzoni.apple.com' with 192.168.2.26 [Info - Server] SiriProxy up and running.
/home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:411:in block in start_tls': Could not find /root/.siriproxy/server.passless.key for start_tls (EventMachine::FileNotFoundException)
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:ineach'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:in start_tls'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/connection/iphone.rb:15:inpost_init'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:58:in block in new'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:ininstance_eval'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:in new'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1467:inevent_callback'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run_machine'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:inrun'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy.rb:17:in initialize'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:innew'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:in start_server'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:90:inrun_server'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:39:in initialize'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:innew'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:in <top (required)>'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:inload'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:in
Hi Elvis,
Thanks for the response. Yes, I ran "siriproxy gencerts" in my pi home directory and then installed it on my phone (along with changing the phone's DNS to be my pi's IP. I noticed that there was an error: "Could not find /root/.siriproxy/server.passless.key for start_tls (EventMachine::FileNotFoundException)"
I never manually created /root/.siriproxy/, and it doesn't currently exist. I created /home/pi/.siriproxy/; in this directory you can find the certs that siriproxy is looking for (this is where I grabbed ca.pem and sent it to my phone).
From my perspective, it looks like siriproxy is looking for a directory and some files that either A) weren't automatically created, or B) there might need to be a new couple lines in the install instructions for this version.
Any other thoughts?
I grabbed this from the old SiriProxy instructions. Give it a try and we can ask Pete to add it to the new instructions. From the error messages, you may have to point the symbolic link the other way around, i.e. while in /root ln -s /home/pi/.siriproxy .siriproxy You also might have to sudo the command to write to the root directory depending on which account you are logged in as. You can test to see if it works by cd /root/.siriproxy and ls and see if it lists the files.
From old instructions:
Note: on some machines, rvmsudo changes "~" to "/root/". This means that you may need to symlink your ".siriproxy" directory to "/root/" in order to get the application to work:
sudo ln -s ~/.siriproxy /root/.siriproxy
I confirmed this problem. I don't get the same problem when I run SP as root.
root@raspberrypi:~# siriproxy server -d 192.168.68.97 -u nobody WARN: Unresolved specs during Gem::Specification.reset: rake (>= 0) WARN: Clearing out unresolved specs. Please report a bug if this causes problems. [Info - Configuration] Loading plugins -- If any fail to load, runsiriproxy bundle(notbundle install) to resolve. {"redeye"=>"living room", "room"=>"living room", "device"=>"tv", "feed"=>"antenna"} Error reading picturejokes.yml file. [Error] Failed to load plugin: PictureJokes [Info - Server] Starting SiriProxy on 0.0.0.0:443... [Info - Server] DNS server is not running yet, waiting 1 second... [Info - Server] DNS Server started, tainting 'guzzoni.apple.com' with 192.168.68.97 [Info - Server] SiriProxy up and running. /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:411:inblock in start_tls': Could not find /root/.siriproxy/server.passless.key for start_tls (EventMachine::FileNotFoundException)
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:in each' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:instart_tls'
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/connection/iphone.rb:15:in post_init' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:58:inblock in new'
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:in instance_eval' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:innew'
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1467:in event_callback' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:inrun_machine'
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy.rb:17:ininitialize'
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:in new' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:instart_server'
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:90:in run_server' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:39:ininitialize'
from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:in new' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:in<top (required)>'
from /usr/local/rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:in load' from /usr/local/rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:ineval' from /usr/local/rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in
I think as long as you do rvmsudo it should preserve the correct location. But in reality I think it would be best to offer an override option for the location of config.yml and the certs. I have been considering using a SQLite DB for storing config options. Could maybe store the certs in there, too.
-Pete
On Mar 14, 2013, at 6:52 PM, Elvis [email protected] wrote:
I confirmed this problem
root@raspberrypi:~# siriproxy server -d 192.168.68.97 -u nobody WARN: Unresolved specs during Gem::Specification.reset: rake (>= 0) WARN: Clearing out unresolved specs. Please report a bug if this causes problems. [Info - Configuration] Loading plugins -- If any fail to load, runsiriproxy bundle(notbundle install) to resolve. {"redeye"=>"living room", "room"=>"living room", "device"=>"tv", "feed"=>"antenna"} Error reading picturejokes.yml file. [Error] Failed to load plugin: PictureJokes [Info - Server] Starting SiriProxy on 0.0.0.0:443... [Info - Server] DNS server is not running yet, waiting 1 second... [Info - Server] DNS Server started, tainting 'guzzoni.apple.com' with 192.168.68.97 [Info - Server] SiriProxy up and running. /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:411:inblock in start_tls': Could not find /root/.siriproxy/server.passless.key for start_tls (EventMachine::FileNotFoundException) from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:in each' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:in start_tls' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/connection/iphone.rb:15:in post_init' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:58:inblock in new' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:in instance_eval' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:in new' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1467:in event_callback' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run_machine' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy.rb:17:in initialize' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:in new' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:in start_server' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:90:in run_server' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:39:in initialize' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:in new' from /usr/local/rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:in' from /usr/local/rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:in load' from /usr/local/rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:in' from /usr/local/rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in eval' from /usr/local/rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in'`
— Reply to this email directly or view it on GitHubhttps://github.com/plamoni/SiriProxy/issues/479#issuecomment-14939954 .
So I tried the sym link, but that didn't seem to work. Even when using absolute paths it seemed to get mad. On the bright side, it seems to be a different error now :)
root@raspberrypi:~# pwd
/root
root@raspberrypi:~# /home/pi/.rvm/bin/rvmsudo /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/siriproxy server -d 192.168.2.26 -u nobody -l 192.128.2.26
Warning: secure_path found in /etc/sudoers, falling back to call via /usr/bin/env, this breaks rules from /etc/sudoers. export rvmsudo_secure_path=1 to avoid the warning./usr/local/rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:296:in to_specs': Could not find 'siriproxy' (>= 0) among 12 total gem(s) (Gem::LoadError) from /usr/local/rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:307:into_spec'
from /usr/local/rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_gem.rb:47:in gem' from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/siriproxy:22:ineval' from /usr/local/rvm/gems/ruby-2.0.0-p0@global/bin/ruby_noexec_wrapper:14:in
That's a different problem.
Warning: secure_path found in /etc/sudoers, falling back to call via /usr/bin/env, this breaks rules from /etc/sudoers. export rvmsudo_secure_path=1 to avoid the warning./usr/local/rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:296:in
Since you are logged in as root you don't need include rvmsudo, but if you insist type the following command.
export rvmsudo_secure_path=1
Good call. Getting back to non-root, it's still giving the tls error:
pi@raspberrypi:~$ rvmsudo siriproxy server -d 192.168.2.26 -u pi -L 192.168.2.26
Warning: can not check /etc/sudoers for secure_path, falling back to call via /usr/bin/env, this breaks rules from /etc/sudoers. export rvmsudo_secure_path=1 to avoid the warning.WARN: Unresolved specs during Gem::Specification.reset:
rake (>= 0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
[Notice - Configuration] ==================== Important Configuration Notice ==========================
[Notice - Configuration] '/root/.siriproxy/config.yml' not found. Using '/home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/config.example.yml'
[Notice - Configuration]
[Notice - Configuration] Remove this message by copying '/home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/config.example.yml' into '~/.siriproxy/'
[Notice - Configuration] ==============================================================================
[Info - Configuration] Loading plugins -- If any fail to load, run siriproxy bundle (not bundle install) to resolve.
[Info - Server] DNS Server started, tainting 'guzzoni.apple.com' with 192.168.2.26
[Info - Server] Starting SiriProxy on 192.168.2.26:443...
[Info - Server] SiriProxy up and running.
/home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:411:in block in start_tls': Could not find /root/.siriproxy/server.passless.key for start_tls (EventMachine::FileNotFoundException) from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:ineach'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:in start_tls' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/connection/iphone.rb:15:inpost_init'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:58:in block in new' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:ininstance_eval'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:in new' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1467:inevent_callback'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run_machine' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:inrun'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy.rb:17:in initialize' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:innew'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:in start_server' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:90:inrun_server'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:39:in initialize' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:innew'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:in <top (required)>' from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:inload'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/siriproxy:23:in <main>' from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:ineval'
from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in `
It seems on some operating systems, using rvmsudo causes ~ to become /root/. I can toss together a new command line option to allow you to override. Give me a few mins.
This turned out to be really tough because of how the configuration is currently managed... Hopefully will get a fix in in a day or two.
Having the same problem and am beating my head against the wall trying to figure it out. Looking forward to any help you might give.
Running from root, transparent dns redirect via dd-wrt, created the symlinks, generated and loaded the certs (over and over). Cant wait to start playing with this!
Hi,
I'm having the same problem too, when running siriproxy with the -u flag. Any progress on this? :)
any solutions for the problem on RasPi ?? i have the same issue :(
"Could not find /root/.siriproxy/server.passless.key"
rvmsudo siriproxy server -d XXX.XXX.XXX.XXX -u pi doesn´t work :(
what does the -L option mean ??
Are you using my Siriproxy SD card image? If so log in a root, drop the rvmsudo and -u option
No, i installed it a day ago myself. the problem is as plamoni sayed here:
It seems on some operating systems, using rvmsudo causes ~ to become /root/. I can toss together a new command line option to allow you to override. Give me a few mins.
i could fix it by changing the ~ with /home/pi/ but that´s not the best way ;)
I agree there needs to be a more robust way. Not sure what the correct answer is but look at #519 for temporary solutions. I use the file expand dir home method in some of my plugins but not sure if it would solve all cases for SiriProxy.
http://stackoverflow.com/questions/2504646/ruby-opening-files-relative-to-home-directory
What ever solution that is suggested it needs to meet the following:
- Ruby and SiriProxy installed as user or root
- Launched as user or root
- Launched with and without the -u option
Just installed elvisimprsntr SD image and running SiriProxy on RasPi, getting the same error is there a solution to this yet?
SiriProxy looks like it loads correctly, then it freezes for several minutes before all the "from /usr" text appears.
root@raspberrypi:~# siriproxy server -d 192.168.1.200
WARN: Unresolved specs during Gem::Specification.reset:
rake (>= 0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
[Info - Configuration] Loading plugins -- If any fail to load, run siriproxy bundle (not bundle install) to resolve.
[Notice - Server] ======================= WARNING: Running as root =============================
[Notice - Server] You should use -l or the config.yml to specify and non-root user to run under
[Notice - Server] Running the server as root is dangerous.
[Notice - Server] ==============================================================================
[Info - Server] Starting SiriProxy on 0.0.0.0:443...
[Info - Server] DNS server is not running yet, waiting 1 second...
[Info - Server] DNS Server started, tainting 'guzzoni.apple.com' with 192.168.1.200
[Info - Server] SiriProxy up and running.
[Info - Plugin Manager] Plugins loaded: Example
/usr/local/rvm/gems/ruby-2.0.0-p195/gems/eventmachine-1.0.3/lib/eventmachine.rb:664:in connect_server': no implicit conversion of nil into String (TypeError) from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/eventmachine-1.0.3/lib/eventmachine.rb:664:inbind_connect'
from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/eventmachine-1.0.3/lib/eventmachine.rb:640:in connect' from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/lib/siriproxy/connection/iphone.rb:38:inssl_handshake_completed'
from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in run_machine' from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:inrun'
from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/lib/siriproxy.rb:17:in initialize' from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/lib/siriproxy/command_line.rb:106:innew'
from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/lib/siriproxy/command_line.rb:106:in start_server' from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/lib/siriproxy/command_line.rb:90:inrun_server'
from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/lib/siriproxy/command_line.rb:39:in initialize' from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/bin/siriproxy:6:innew'
from /usr/local/rvm/gems/ruby-2.0.0-p195/gems/siriproxy-0.5.4/bin/siriproxy:6:in <top (required)>' from /usr/local/rvm/gems/ruby-2.0.0-p195/bin/siriproxy:23:inload'
from /usr/local/rvm/gems/ruby-2.0.0-p195/bin/siriproxy:23:in <main>' from /usr/local/rvm/gems/ruby-2.0.0-p195/bin/ruby_noexec_wrapper:14:ineval'
from /usr/local/rvm/gems/ruby-2.0.0-p195/bin/ruby_noexec_wrapper:14:in `
I tested the my SD card image and did not have any problems running as root from the /root directory. Did you run any other commands or change any files?
What do you mean when you say from the /root directory??
I ssh using root into my Pi when i cd to root directory and ls it it is empty is this normal / correct?
root@raspberrypi:/# ls bin boot boot.bak dev etc home lib lost+found media mnt opt proc root run sbin selinux srv sys tmp usr var root@raspberrypi:/# cd root root@raspberrypi:~# ls root@raspberrypi:~#
Only things that i have changed are that I SSH into my RasPi using a static eth0. I change the DNS on my iPhone to match my Pi IP. Also added some plugins to siriproxy config.yml
- Launch SiriProxy from the default directory for the root account. Do not CD to any other directory.
- Did test SiriProxy BEFORE adding plugins?
I launch siriproxy from default directory after i log in as root using the following command
siriproxy server –d 192.168.1.200
The error code i posted first was before i had added any plugins to the config.yml
I assume you installed the certificate on your iOS device. Try generating new certs