I get an error message when I try to sign up.
WE'RE SORRY, SOMETHING WENT WRONG WHEN ATTEMPTING TO SIGN UP. PLEASE CHECK YOUR INTERNET CONNECTION
I'm on the desktop version for windows 10.
My company has a proxy setup that often causes problems... Does anyone know if I can configure Neo4j to use the proxy? Thanks in advance.
Edit. Cheers for the downvotes...
Use the log via github account option and it works.
Related
For e.g. when clicking the link within email, I got redirected in browser to http://0.0.11.184/users/confirmation?confirmation_token=rcqn2fYMdAYYwZ-d_fXh
with error message:
This site can’t be reached
The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET
I have my entire repo up at https://github.com/cheese1884/197451.git as I'm not sure which codes I am to post up online here for possible faults. Just need this to work in development mode.
Found the solution in Mailcatcher. Thanks guys!
I have got my application working fine with the standalone MAPI (1.2.1 CDO) however after removing that and installing Outlook, I cannot get it working.
I get a MAPI_E_NETWORK_ERROR, which when I catch and return the exception message caught comes up with
System.Runtime.InteropServices.COMException: Not logged on. Please log on first
Do I have to do anything different to get this working with an outlook installation? This is thrown when doing
LogonExchangeMailbox(username, exserver)
MAPI_E_NETWORK_ERROR is a network access error. Is firewall active on that machine? Was your app added to the exclusion list?
It could also be the name of the exchange server not being correct. I had this issue as the old exchange server had been decommissioned so rather than being EXHANGE.ad.{company}.com it changed to just the new server name e.g. EXCHANGEABC12.
Also keep in mind that LogonExchangeMailbox connect using plain old RPC protocol. If you are connecting to Exchange 2013/2016 over RPC-over-HTTP, you need to use LogonHostedExchangeMailbox .
I installed the spicework window setup on my server 2008. Here is the URL http://ffrsdevserver.com:9675/portal for my dev server. It works fine on my(Indian) system, other systems of my company, my mobile device with 3G network.
My client in USA said it not worked for him. I verify this by login to server located in USA. on server's browser i got error ERR_CONNECTION_TIMED_OUT Can anybody suggest how can i fix it, I searched a lot on google and spicework community but nothing worked for me.
I found that my port 9675 was closed. I open the port and it fix my problem. Thanks :)
I'm working on a Rails API for an iOS app. I was able to run it on my localhost and consume it from the iPhone simulator but now I want to test on the device. I successfully pushed to heroku and changed my ROOT_URL to be the one that it provided. Now when I visit the application URL (http://sleepy-lake-5504.herokuapp.com/v1/users if you really wanted to know), I get the error message:
Application Error
An error occurred in the application and your page could not be served. Please try again in a few moments.
instead of JSON data.
Am I doing something wrong? Do I need to do something special with heroku to hit it as an API?
Needless to say it's making me very sad.
Any help is appreciated.
You can create a tunnel to your localhost using ngrok. Ngrok will forward your localhost and give you a URL which you can use in your iPhone.
This will help you to debug your localhost without actually hosting your site so that you get a better idea of whats going wrong. Let me know if that helps.
Does anyone know how to fix this issue? I keep on getting this error from Twitter when I try to login on our app. This was happening since May 23, 2013.
Whoa there! The request token for this page is invalid. It may have
already been used, or expired because it is too old. Please go back to
the site or application that sent you here and try again; it was
probably just a mistake.
I also saw some users experiencing this issue in this link
Thanks a lot!
Just throwing it out there. Have you tried resetting the keys in your application management page? Or recreate your access token? (Unless the "Reset keys" option does this also).