Im trying to install socket.io throu yeoman, it loads sockets just fine when then I guess it tries to load up the dependencies and it can't find them and gives me fatal error ws not found (for the ws package).
It's trying to fetch from theses urls:
bower.herokuapp.com/packages/uglify-js
bower.herokuapp.com/packages/ws
bower.herokuapp.com/packages/xmlhttprequest
bower.herokuapp.com/packages/active-x-obfuscator
and it's cant find the links to GIT. i've tried to load the addresses but there is no response from the server.
Any idea how I can fix that problem?
Thanks
socket.io is not a valid Bower component. I've request it be removed from the registry.
It's a component component, not a Bower component. (confusing, I know...).
Related
I'm developing an offline Android app with Genexus Ev3 U9 and when I try the app in the device I see there is no initial synchronization, even when I try to execute a manual sync the app shuts down. The cat log shows that request made to URLs like http://192.168.12.17/MyAppSmartDevicesEnvironment/gxmetadata/MyApp.android.json
worked fine but when the app tries to get this URL http://192.168.12.17/MyAppSmartDevicesEnvironment/rest/MyAppOfflineDatabase?fmt=json&event=gxchecksync returns 404 I tried the same link in my laptop and it's like the requested resource was not created by GeneXus.
What could be wrong?
There are actually a couple of things you might want to check.
When you accessed http://192.168.12.17/MyAppSmartDevicesEnvironment/gxmetadata/MyApp.android.json you got data but that just means that the virtual directory was successfully created. (which is good of course)
Then you need to check if the WCF module is installed correctly, in order to do that you could try to go to http://192.168.12.17/MyAppSmartDevicesEnvironment/MyAppOfflineDatabase.svc/rest or any other service in your KB. That goes straight to the service implementation. (you can check you web.config file in order to see the actual rewriting rules)
If that works it's certainly a URL Rewrite problem like Sandro and Guscarr suggested.
You can download and install the module from here: http://www.iis.net/downloads/microsoft/url-rewrite
Gcastano,
It seems that you're generating to .net, right?
If so, it could be some problem with iis rewrite module.
Anyway you might check gx software requirements...
It seems that REST services cannot be run on your IIS, as Sandro said, try installing URLRewrite.
Further info at http://wiki.genexus.com/commwiki/servlet/wiki?14575,Android%20-%20FAQ%20and%20Common%20Issues
I managed to configure stand alone Parse server for my Android app using ubuntu server and mongoDB. And now Parse released its open source dashboard for parse server which I am able to setup but getting error in accessing it remotely.
As it says "Parse Dashboard can only be remotely accessed via HTTPS". I have almost no experience of developing web app. I have tried changing http to https in url but it didn't worked!
I have also tried adding username and password for basic auth, but it didn't worked either! Here's link for parse dashboard
https://github.com/ParsePlatform/parse-dashboard
Try starting the dashboard like this:
export PARSE_DASHBOARD_ALLOW_INSECURE_HTTP=1
npm run dashboard
I have the same problem. I set up the parse server through heroku. I tried antsyawn's suggestion, it did not work. The github to parse-dashboard just updated a little more.
Now you should:
npm install -g parse-dashboard
parse-dashboard --appId yourAppId --masterKey yourMasterKey --serverURL "https://example.com/parse" --appName optionalName
They did suggested to add --allowInsecureHTTP=1
Nevertheless, I tried all that as well and its not working. May be you can try this too since you set up your server differently(it might work).
im working with ParseServer And ParseDashboard to Start we cant create confused about two.
For me , more important is ParseDashboard, And yes you can acess Remotely, firstly you need create a hack direct in code to do that.
To run parse dashboard without problems follow this steps.
git clone git#github.com:ParsePlatform/parse-dashboard.git
cd parse-dashboard
npm install
After this! after!...
npm run dashboard
This screen will be showed to you...
When this image is running you can acess by url your serverIp:4040 will show dashboard.
dashboard is running.
The answer from #xiaowoo worked for me. For a visual, I watched this video
Install Parse Server and Parse Dashboard to Digital Ocean
In summary, here is what I ended up running:
parse-dashboard --appId MyApp --masterKey mysupersecretmasterkey --serverURL "https://198.58.10.23/parse" --appName TestApp --allowInsecureHTTP=1
Server response:
The dashboard is now available at http://0.0.0.0:4040/
Browse to your dashboard:
http://198.58.10.23:4040
I'm new here. I've tried all I could but couldn't setup my laravel app. I've also tried the solutions provided here
How to install Laravel 4 to a web host subfolder without publicly exposing /app/ folder?
but I keep on getting HTTP Error 500.0 - Internal Server Error The page cannot be displayed because an internal server error has occurred.Any help please?
change your host php version
PHP >= 5.4
MCrypt PHP Extension
http://laravel.com/docs/4.2#server-requirements
Consider using Forge, it saves you a lot of time and you would support the creator
Basically what the title says ;).
I've seen an npm package for Express (https://www.npmjs.org/package/heroku-ssl-redirect), but not for MeteorJS.
Assuming you have configured SSL this package should come handy
meteor add force-ssl
It worked on 0.9.4, I'm not sure it's working now
I have a node.js server using socket.io. The idea is to allow two different html files to communicate information to each other through this server. All was well with socket.io ver0.9.16 until ver 1.0 came out. Now, I receive a few errors on both the client and server side, the most apparent (to me, since I am new to this) is the ERR_NAME_NOT_RESOLVED error that I find when I start up the locally hosted server.js file and attempt to connect to it through the client html.
When I open the console in Google Chrome, I find this error which prints again to the console every second or so:
GET http://file/socket.io/?EIO=2&transport=polling&t=1406247171961-0 net::ERR_NAME_NOT_RESOLVED
What follows are snippets of places where I may have problems in my html and server.js files as well as in a js file that is used by my html file to connect to the server.
index.html
I think this bit of code gets the socket.io client code from the localhost server. This is the first place where I may think that I have a problem
<script src="http://localhost:4000/socket.io/socket.io.js "></script>
In addition, the following is where I import my index.js file which is used to connect to the server
<script type="text/javascript" src="scriptsTeacher.js" ></script>
-
server.js
This code (according to my sources) should set up a server on the localhost with port 4000 to which clients can connect and send/receive information
var io;
io = require('socket.io').listen(4000);
io.on('connection', function(socket)
{
console.log("user connected");
});
-
index.js
This code is used by the index.html which has it connect to a server listening on port 4000 using socket.io.
var socket = io.connect('localhost:4000');
-
Currently, there are two blatant errors that I can find. They are probably not the root of the problem, but they are as far as my limited debugging experience can take me.
ERR_NAME_NOT_RESOLVED: (NOTE: I have looked at socket.io ERR_NAME_NOT_RESOLVED and it was not entirely useful since that user had a typo by using http:\\ instead of http://). As stated before, when opening index.html in Google Chrome and accessing the console, I receive multiple ERR_NAME_NOT_RESOLVED errors.
There is no "Welcome to socket.io" message when accessing localhost:4000 I am certain that there should be such a message. Note that there is no 404 error, when I start up the server, I can access that webpage, but it is blank. If the server is not running, then I do get a "Webpage not found" message.
My question is this: Is there anything that I am not doing but should? As I said, I am new to this, and after some hunting around on the internet, I have a suspicion that there is some server (HTTP, Express, Express 3/4?) that I am not establishing. However, it is of note that the code worked as is in ver0.9.16 (using the .socket() and .listen() functions which were removed from my code for migration to ver1.0). If there is any information that is missing, I will do my best to provide it as soon as possible.
-
I am using:
Macintosh OS 10.6.8
Google Chrome version 36.0.1985.125
socket.io ver1.0
node.js v0.10.29
The address in the error is wrong (assuming you haven't set up a local name resolver).
The address in the error begins with:
file
When it should begin with something like:
localhost:4000
The issue is probably in some of the js-config files for the web application (not the server). Or maybe you're trying to access the file locally (eg. just open the html-file in the browser) instead of typing the address localhost:4000.
I had the same problem that running file in the browser:
eg.
"file:///C:/apppath/index.html"
Try running from the server
eg.
"http://your.app:4000/index.html"
I had the same issue - I wasn't able to connect to my socket.io server through my client on the same machine on mac. I disabled the firewall and it resolved the issue. I guess we could use xhr-polling instead and overcome this.
Vikram
I ran into a similar problem, but the solution to my problem had nothing to do with CORS. In my case, which is a Cordova 4.0.0 app using socket.io, I was using an incorrect URL for the socket server. I was using a socket server URL like this:
//socketserver.example.com:8000
This worked fine in the desktop Chrome browser, but in the Cordova webview on the phone or emulator there were many errors regarding failed GET and POST requests to a URL that started with
http://file/socket.io
The correct URL in my case turned out to be:
http://socketserver.example.com:8000
Note the complete scheme at the beginning of the URL.