That I can’t say… I have ran mine on a Linux Box (Mint) and RPi (current method) and even in Windows 10… and have NEVER had to run that command. I handle all port forwarding via my router… so probaly nothing like how a VPS works.
virtual private server:
think of it like a vmWare server… One big massive server (called a hypervisor / ESX host) that has a bunch of little servers under it. Not all of them use the ram at the same time or the diskspace (or the bandwidth)
In the end, its just a machine that runs under another.
I know im off topic here gunner, but you have always seemed eager to experiment. you have to give this one a go once, just to see what it does.
There are a ton to pick from. it appears the most recent, popular one, is https://www.virtualbox.org/
@pkarun, sorry for sidetracking our post here, gunner got me over the hump when i started with bynk, so i hope to someday return the favor.
How you doing on your iptables?
03:12:53.784 INFO - Using data dir '/home/pi/Blynk'
03:12:54.732 INFO - Region : local. Host : 10.47.0.5.
03:12:54.792 INFO - Using native epoll transport.
03:12:55.495 INFO - Initializing gmail smtp mail transport. Username : firstname.lastname@example.org. SMTP host : smtp.gmail.com:587
03:12:55.564 INFO - Reports : 0
03:12:55.571 INFO - Didn't find custom user certificates.
03:12:55.574 INFO - Didn't find Let's Encrypt certificates.
03:12:55.581 WARN - You didn't specified 'server.host' or 'contact.email' properties in server.properties file. Automatic certificate generation is turned off. Please specify above properties for automatic certificates retrieval.
03:12:55.582 INFO - Using native openSSL provider.
03:12:55.582 WARN - ATTENTION. Server certificate paths (cert : '/root', key : '/root') not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
03:12:56.382 INFO - HTTP API and WebSockets server listening at 8080 port.
03:12:56.384 INFO - HTTPS API, WebSockets and Admin page server listening at 9443 port.
03:12:56.385 INFO - Mqtt hardware server listening at 8440 port.
Below are the commands that I followed to install blynk on my server:
Heh… I actually knew that part. I just guess I am a bit of an oldskool geek, I like my Local Servers to be Local and see no benefit in paying all sorts of additional monthly subscriptions for something small like a Blynk Server that I can just as easily have on existing hardware for $free.nintynine And still access it on all the globetrotting outings I do every 2nd Sunday… Well… I believe I could… there is still that whole “Get dressed and leave the house” issue to work on…
Strange as it might seem, what with using Blynk for over two years and living in this forum most every day… I am not as into IoT and IoT connected everything including the toilet paper roll as some… I use Blynk mostly for the GUI
But rest assured, as I find needs & resources to learn something, I can, will and do
My answer to this question is, YES. We can run apache and blynk on the same server (as per my test result on test server setup).
We can still access Blynk server without actually running port forwarding commands.
Thanks @lvennard I was actually missing this step on my server so I was not able to access my blynk admin page. After running a few test server setup, I noticed I need to run those commands to enable 8080 and 9443 ports on my ubuntu server.
Thanks a lot.
Yes. This is another thing that I missed during accessing the blynk server admin page. Thanks a lot, @Gunner for pointing the issue.
Finally, I successfully setup blynk on my VPS.
I was actually trying to install blynk on my VPS several days but I’m failing by missing those two-steps. Finally, I thought to post here after trying all possible ways. Anyway, really thanks @Gunner and @lvennard for helping.