Open toughbunny opened 10 years ago
Hi,
Here is an update with pictures. I forgot to add that when I use sudo, I just get a blank screen like in the last picture.
It looks like the file permissions/ownership on the file ./bin/wigle_credentials.txt do not allow you to write to it.
Rogan
On 27 March 2014 19:00:09 SAST, toughbunny notifications@github.com wrote:
Hi,
Here is an update with pictures. I forgot to add that when I use sudo, I just get a blank screen like in the last picture.
Reply to this email directly or view it on GitHub: https://github.com/sensepost/Snoopy/issues/4#issuecomment-38831019
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Thanks, But now I have another problem. I fixed the permissions for the two files, wigle_creds and openvpn-status.log files, and all the other files in the /home/woodstock/snoopy/server/bin directory. Now when I type snoopy, I just get a blank screen like in the last picture.
Thanks!
Sorry,
I forgot to add that when I scroll up from the blank screen, I see the following error:
^CTraceback (most recent call last):
File "bin/vpn_drones.py", line 14, in
* Ouch! Exiting *
Sorry again,
This time I left the command running for longer before interrupting and got:
^CTraceback (most recent call last):
File "bin/vpn_drones.py", line 13, in
* Ouch! Exiting *
Thanks Again
Just don't use koding. Try it on a digitalocean droplet with at leat 1gb of ram and see if the problems persist.
Hi,
Thanks Matznerd, but koding is free and you have to pay for digitalocean. Also, there has to be some traceable error here. I would like to keep on trying with koding.
Thanks!
Hi, I just wanted to say that I've isolated the problem. When I don't give read permissions to /etc/openvpn/openvpn-status.log, the the command to start snoopy server components from the server menu, it stops the server right after with a permissions denied error. But when I do give read permissions, the command snoopy just returns a blank screen.
Thanks!
Hi,
I installed snoopy on a web-based vm on koding.com, which is both 64-bit and not the recommended version of ubuntu (13), so I knew that this would lead to problems. However, since the install, I am not able to do much with the menus because it keeps aborting my commands with errno 13 permission denied, including just starting the server on managing drone configuration packs.
Thanks!