Gencerts not working correctly on new release? #479
Comments
|
Did you generate the certificates? |
|
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 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.
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'`
|
|
I think as long as you do rvmsudo it should preserve the correct location. -Pete On Mar 14, 2013, at 6:52 PM, Elvis notifications@github.com wrote: I confirmed this problem root@raspberrypi:~# siriproxy server -d 192.168.68.97 -u nobody — |
|
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: from /usr/local/rvm/gems/ruby-2.0.0-p0@global/bin/ruby_noexec_wrapper:14:in eval' from /usr/local/rvm/gems/ruby-2.0.0-p0@global/bin/ruby_noexec_wrapper:14:in'root@raspberrypi:~# |
|
That's a different problem. 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: pi@raspberrypi:~$ |
|
Are you using my SD card image or did you install it yourself? |
|
I installed this myself |
|
It seems on some operating systems, using |
|
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. |
|
Cool - thanks Pete! |
|
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? :) |
|
same problem here! |
|
any solutions for the problem on RasPi ?? i have the same issue :( "Could not find /root/.siriproxy/server.passless.key" |
|
Yes. Drop the -u option |
|
rvmsudo siriproxy server -d XXX.XXX.XXX.XXX -u pi 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. |
|
What ever solution that is suggested it needs to meet the following:
|
|
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: root@raspberrypi:# |
|
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 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 |
|
|
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 |
|
And install the new cert on the iOS device. |
|
And delete the old one |
|
Generated new Cert. Removed all old ones from my iOS and added new one. Then changed DNS in wifi settings to match RasPi IP. SiriProxy starts ok but siri on my phone just spins round and round and does nothing at all, no messages appearing on SiriProxy. When i press ctrl+c to exit SiriProxy the 'from /usr ...' error messages then appear. |
|
Error message after you use ctrl-c to stop SiriProxy are expected because you interrupted the process. Try turning off cellular data, toggle airplane mode off for 5 seconds, confirm the DNS entry is still set to the RPi. Then launch SiriProxy and activate Siri on your iOS device. It might take one or two tries to get Siri to connect to SiriProxy the first time. |
|
Also what iOS and model iPhone are you using and is it jailbroken? |
|
Just tried what you recommended still not response from SiriProxy. I tried numerous times with Siri. I am running iPhone 5 - iOS 6.1.2 - Not Jailbroken |
|
Try using Siri without SiriProxy on your local WiFi to confirm that Apple is not blocking your ISP IP/UUID |
|
I managed to solve by linking my ~/.siriproxy to /root/.siriproxy, then don't use -u on command line or user:XXXX in config.yml. That way I can run with rvmsudo. |
|
I wonder of it might be better to use the $HOME environment variable instead of the |
|
Ended up installing a fresh image but i then install dnsmasq and it all works fine now?!? Thank you for your support :) |
|
Thanks for all the help everyone! Should I leave this as an open issue or close it out? |
|
leave open for now. |
|
It's working for me. I did struggle with this error and a few other issues with DNS. I am a few weeks into Pi, Linux and 2 days into ruby so I don't know whether the below is useful.... I chose to go the hard route of doing the install myself as i have been building up my system and incrementally backing up. If it helps I had 3 goes at this I first tried the python port and couldn't get that working (didn't want to learn ruby, as I am only just into python). Tried Elvis' instructions https://gist.github.com/elvisimprsntr/4409751 (thank you by the way) but did something wrong, did it again but this time used sudo apt-get for any of the installs supported by it (e.g. wired [I think can't remember now]) as I saw some errors first time around. I also tried easy_install for siriproxy but didn't have much luck. Overjoyed it's working - thank you, it's awesome. Backing up furiously as I really wouldn't want to go through the rvm install again ;-) |
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
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 `'
The text was updated successfully, but these errors were encountered: