I am running my web app on localhost and I have need to use ns so that chat and messaging, etc could work! now the WebSocket filed to connect! how can I fix that on localhost? anyone?
You can use Pusher.com. I use it for my local development. It is free and works great. It is already supported by Laravel just read this https://laravel.com/docs/8.x/broadcasting#pusher-channels
Related
I have a web application developed in PHP and all users can access it via local network(xampp), now the users want to access their gmail,yahoo or any emails via localhost(xampp), I want something like MS-outlook to work in my xampp.
is there any solution ?
the propper way to do this is if you use email server at localhost better already install apache2 in your own device
also using postfix and dovecot will be very helpfull here some link
about webmail configuration in google cloud instance
https://medium.com/geekculture/how-to-host-a-personal-email-server-on-google-cloud-for-free-part-i-8124d65d1d25
perhaps that concept will help you to develop your own webmail in Local Area Network
have an app with a successfull kurento implementation connecting to a rstp://ip and displaying it to a video tag on my web page, just like this
http://www.kurento.org/blog/interoperating-webrtc-and-ip-cameras
https://github.com/lulop-k/kurento-rtsp2webrtc
it works like a charm on my localhost but once i deploy it to heroku and test it... well, it just does not display any video, no errors or weird issues it just does not display video, i'm not sure if there is something i missed to config on my kurento server like a cors config or similar and i've been looking for it with no luck so... any insight or guidance would be helpfull.
btw i have my kurento media server running on an amazon ec2 micro instance and my client running on heroku
Thanks in advance
I had the same problem!! I solved it using HTTPS instead of HTTP :)
I have an Technicolor TG789vn v3 modem and it have built in router, which I don't need at all.
So by going to my localhost I see router login page.
Using xampp on windows 7 btw.
And since it's nice to play with small pages on local I would be more than happy to remove this router login from my localhost.
Ok, turns out it was the wrong IP I was accessing.
How to find your real IP: Microsoft sometimes actually helps.
I have a Heroku application that binds with a telco sms gateway via SMPP
The telco guys need to whitelist IPs for my app to connect.
I am aware of the new addon proximo, but it's just insanely priced. So that option is out.
Is there a subnet or a list of IPs that I can get whitelisted and is there a guarantee that all requests from my app will originate from tose IPs?
I found this https://api.heroku.com/vendor/logplex/allowlist.
Is that only for syslog or all apps make a request from one of those IPs?
Thanks
There is now a Heroku add-on that does this called Proximo: https://addons.heroku.com/proximo
The Heroku docs specifically mention how dynos don't have static IP addresses. Even when using custom domains it looks like they want you to point to a CNAME record rather than an IP address. So if you need a static IP it looks like Proximo is your best bet.
Would it be possible to use an API token to authenticate your app with the sms gateway, similar to the way the blitz.ip plugin works with heroku? Then you might not need to use a static IP whitelist.
This question looks to be doing something similar to you, and this answer suggests using a hosted VPN service. Would that work?
Heroku now has Private Spaces which is what you are looking for:
https://www.heroku.com/private-spaces
Another Heroku addon option is Quotaguard , in beta, free for now.
Answering my own question. Even though an external VPN or the proximo addon are a solution in case you want to whitelist a Heroku app, I have decided to go for the simpler option and host the SMPP binding service of my app on ec2 using an Elastic IP
You can host a proxy yourself using Dockhero Heroku add-on - https://dockhero.io/ - which has a static IP (AWS elastic IP).
Install the add-on and the CLI plugin:
$ heroku addons:create dockhero
$ heroku plugins:install dockhero
Wait until the provisioning is done and get DOCKHERO_HOST environment variable
$ heroku dh:wait
$ heroku config:get DOCKHERO_HOST
--> e.g. dockhero-spherical-42047.dockhero.io
Create dockhero-compose.yml file with the following contents:
version: "2"
services:
proxy:
image: tecnativa/tcp-proxy
environment:
LISTEN: ":80"
TALK: "www.wikipedia.org:80"
ports:
- "80:80"
Here www.wikipedia.org:80 is the server which you build a proxy for.
Find more about the syntax in https://docs.docker.com/compose/compose-file/compose-file-v2/
Run this stack in the cloud using Dockhero CLI:
$ heroku dh:compose up -d
Any requests to the host from DOCKHERO_HOST Heroku config var will now be proxied according to your dockhero-compose.yml
$ curl http://dockhero-spherical-42047.dockhero.io/
--> <response from www.wikipedia.org>
IMPORTANT: as of writing this, dockhero.io is in Beta and available for free. When switching to production, the assigned IP may be changed after a prior notification.
Fixie is another alternative add-on not mentioned here. Free plan with 500 requests per month. Requires some adjustments in code and heroku app to be in us region (or you can migrate it: Migrating an Application to Another Region). Worked for me.
I have a basic chat socket.io node.js application working on the localhost of a Windows server running Windows 7.
Node and Socket.io installed without any issue and when I run my application through RDC to the windows server, the socket works perfectly.
What I'm struggling with is how i access the socket e.g. "socket.io/socket.io.js" externally.
I would have assumed it would be rather than "localhost:8000/socket.io/socket.io.js" it owuld be "{server_ip}:8000/socket.io/socket.io.js" however this does work.
I saw some discussion about iisnode, but it seems that sockets arent supported yet with that implementation.
Any suggestions?
You can use socket.io with iisnode, however you will not be able to use the websockets transport since IIS 7 does not support websockets. You must explicitly configure your iisnode-hosted socket.io server to use the xhr-polling transport instead.
It turned out to be a firewall issue that was blocking access to that port which my hosting company managed to resolve for me so I'm using socket.io in the normal manner through a node command prompt.
Thanks for the advice, I did try Iisnode and like you said found that sockets weren't supported.