@Tippon Yeah, that’s pretty much it. The mirror attempts to connect to my command & control server at DNS entry that I control. When it connects, it establishes a reverse SSH connection. I can ride that reverse SSH connection down into the mirror. The C&C server is cloud based, so I just turn it off whenever I don’t need to connect to the mirrors.

Because it’s the mirror making the outgoing connection, firewalls let it pass by. All the mirror needs is a connection to the internet.

I have a pretty long tutorial on how to set it up. I’m a bit verbose.

From the page you linked:

Options:
--merge-logs                 do not postfix log file with process id
--log-date-format    prefix logs with formated timestamp
-l --log [path]              specify entire log file (error and out are both included)
-o --output            specify out log file
-e --error             specify error log file

So…

pm2 stop mm
pm2 start mm -o "/dev/null" -e "/dev/null"
pm2 save

@aecandroid - Please check out this guide on how to use the markdown features of the forum. Then go back and properly block out your config.js file. That will make debugging your code much easier.

@sdetweil Now this sounds interesting. Do you have tutorial or URL where I can learn how to set this up?

@Anhalter42 said in CORS using node_helper.js for Uber and Lyft APIs:

(or by pressing some shortcut which I forgot; search the forum if you want to know).

Try F12.

@Lorenz - You can configure your mirror to use the built-in Chromium browser instead of electron. You’ll need to do the following:

1. modify your startup script to go node serveronly instead of the usual npm start.
2. Set the home page of the chromium browser to http://localhost:8080.
3. Put the browser into kiosk mode.
4. Set the browser to start on boot.

Please use the Markdown features to post code and console output. It makes it so much easier to read.

@jade said in Config.js file Syntax:

now I have a working mirror that sporadically gives me game of thrones quotes! My office at work is now much brighter!

Well, you do until he kills off another Stark child.

For what it’s worth:

Hardware: BCM2835
Revision: a02082

And I do not have the problem.

@hall1458 Wow. Dude, I’m sorry that nobody has stepped in to help you out. I’m not much of a *nix guy, but I’ve been dealing with this at work for various reasons. I’ll do what I can.

The NTP service should synchronize your Pi’s clock with one of many time servers out on the internet. If you get a terminal onto your Pi and type ps ax | grep ntpd you should see this line in return: 602 ? Ss 0:04 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111. Some parts will be different. This is good. If all you see is grep --color=auto ntp then the NTP service isn’t running. Post back here and we’ll get that fixed.

Assuming that NTP is running on your pi, you will want to check the configuration of your NTP server. Type nano /etc/ntp.conf. If you see a blank screen/file, then you have a problem. Assuming you do see a file, you want to look for the following lines:

# pool: 
server 0.debian.pool.ntp.org iburst
server 1.debian.pool.ntp.org iburst
server 2.debian.pool.ntp.org iburst
server 3.debian.pool.ntp.org iburst

These are the servers that your Pi will be checking for a valid time. You can manually check them as well. Exit the /etc/ntp.conf file and type ntpq -pn and wait. You should see something like this:

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+173.71.73.207   .PPS.            1 u  856 1024  377   18.624   -1.660   5.766
+66.228.59.187   128.59.0.245     2 u  468 1024  377   27.636    0.276   6.356
*199.102.46.76   .GPS.            1 u  839 1024  377   37.422    0.189   4.440
+23.239.24.67    200.98.196.212   2 u  713 1024  377   48.940   -1.173   2.743

At least one of those lines should have an asterisk at the beginning. Give it a go and report back.