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 <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 `'
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
(notbundle 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:in
each' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:409:instart_tls' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/connection/iphone.rb:15:in
post_init' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:58:inblock in new' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:in
instance_eval' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/em/connection.rb:49:innew' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1467:in
event_callback' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:inrun_machine' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
run' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy.rb:17:ininitialize' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:in
new' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:106:instart_server' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:90:in
run_server' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/lib/siriproxy/command_line.rb:39:ininitialize' from /home/pi/.rvm/gems/ruby-2.0.0-p0/gems/siriproxy-0.5.2/bin/siriproxy:6:in
new' 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:in
load' 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:in
eval' from /home/pi/.rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in `