I'm trying to use SignalR in ASP.NET Core 5; I've added SignalR service in service configuration and also created a hub class and its method with Angular, which is also configured as I saw on websites there codes similar but still getting below error please some help me:
Error: Failed to start the connection:
Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled.
This Previous question was from me ,Actually from 4 days i was facing issue in signalr Configuration but the error issue Reason was Port Number Incidently i changed My port number from application properties (Debug Properties) but forgot to change the application path in angular signalR configuration which was not showing any cores issue and i was being confused for 4 days. << I changed angular signalR Configuration withUrl path to right path and issue resolved
Related
I am receiving this error:
A connection attempt failed because the connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to respond xxx.xxx.xx.xx:25
Any ideas?
Note: The credentials are good.
Also, if I use MailKit with .net core 1.0 its working just fine but the project needs upgrading to .net 2.
Thank you very much.
The account is the same. What I noticed is that I get the same error message if I put bogus credentials instead of good ones.
It's the credentials that are not passed the right way. But I cannot explain why the same code is working in the .Net Core 1.0 project. Regarding the code used is just a simple call to smtp server from MailKit samples
`client.LocalDomain = _domain;
client.Connect(_smtpServer, 25, SecureSocketOptions.None);
client.AuthenticationMechanisms.Remove("XOAUTH2");
client.Authenticate(credentials);
client.Send(Message);`
I am trying to do a testcase dealing with webservice REST in hosted Ape 5.0 Environment (apex.oracle.com).
There is a preinstalled Web Service in the Workspace "oracle.example.hr".
I have managed to call that Service from my Browsers URL.
But when i create a Web Service Reference to use that Service for an APEX Page, I receive the Errors:
ORA-29273: HTTP request failed
ORA-29024: Certificate validation failure
I am using the Oracle hosted Environment apex.oracle.com; thus I cannot apply ACLs etc.
Any suggestions?
Kind Regards,
Andreas Resch
Are you using https?
It seems that you are using a client that checks if the certificates are valid.
You can either solve the problem on the server (that is not configured with the correct certificate or configure the client to ignore this problem).
First I'd like to apologize if this question has already been answered on other posts.
I'm pretty new in WebSockets and WebRTC and here's my scenario.
I created an MVC4 application in VS 2012 and install the a sample WebRTC project via nuget package manager console (followed the steps here: http://xsockets.net/blog/tutorial-building-a-multivideo-chat-with-webrtc).
This seems to work fine on my local machine. I deployed the code on our https server (running on IIS6) and I changed the connection string to handle the https connection (code below:)
peerBroker = new XSockets.WebSocket("wss://mydomain.com:443/CustomBroker");
I then hit the URL and I got an error that says:
WebSocket connection to 'wss://mydomain.com/CustomBroker' failed: Error during WebSocket handshake: Unexpected response code: 401
Does anyone have an idea as to what I'm missing here?
You cant just change the connectionstring to be wss.
Have you configured XSockets to run over wss?
See XSockets Configuration
we are doing worklight app on a android and a desktopenvironment(for facebook) that works fine on the liberty profile server (developer worklight environment).
Know we need to post this app on Facebook but to do this we need to use the https protocol on our WAS server, to do this we set the ip, port, protocol: to our external server, and deploy our app with build for remote server, but when the app tried to call an adapter on the server, the Firefox console returns us this:
[09:58:50.675] "response [https://[publicIP]:[port]/WorklightPocProj/apps/services/../../invoke] success: /*-secure-
{"challenges":{"wl_antiXSRFRealm":{"WL-Instance-Id":"ih80d8pjg6la8ubccb7503b936"}}}*/"
and
[09:58:50.675] "defaultOptions:onFailure Procedure invocation error."
The application security on our WAS server is disabled and the ip/port are reachable too.
if i add to the XML adapter on the procedures securityTest="wl_unprotected" the app runs correctly, but i don't to do this workaround
Is there any configuration that we are missing on the app or in our WAS server?
A lot of time since this question but just for trying to help people that hit this question because of the search "defaultOptions:onFailure Procedure invocation error".
Also facing this issue in Worklight 6.1
In my case I faced this issue because I had the following configuration in the adapter .xml:
<procedure name="anyMethod"></procedure>
This works in the development server, but in a stand alone server (at least in WAS) you have to change it for:
<procedure name="submitAuthentication" securityTest="wl_unprotected"></procedure>
In both cases it is unprotected.
Background: I've been tasked with creating a single sign on solution which will redirect our internal users to a vendor's web application. I've set it up as an ASP.Net project which will call a web service provided by the vendor. This service will return a URL and a token to be used to sign in to the vendor's site. All this is to be done securely.
Problem: When using Visual Studio's Add Web Reference dialog to download the WSDL and generate the required proxy class, I get the following error:
There was an error downloading
'https://server:port/folder/Service?wsdl'. The
underlying connection was closed: An unexpected error occurred on a
send. Authentication failed because the remote party has closed the
transport stream. Metadata contains a reference that cannot be
resolved:
'https://server:port/folder/Service?wsdl'. An
error occurred while making the HTTP request to
https://server:port/folder/Service?wsdl. This
could be due to the fact that the server certificate is not configured
properly with HTTP.SYS in the HTTPS case. This could also be caused by
a mismatch of the security binding between the client and the server.
The underlying connection was closed: An unexpected error occurred on
a send. Authentication failed because the remote party has closed the
transport stream. If the service is defined in the current solution,
try building the solution and adding the service reference again.
In addition to this error, the Add Reference button is grayed out, preventing me from adding the reference and generating the proxy class.
The project is running under .Net Framework 4.0. I've downloaded and installed the necessary client keys/certificates correctly. I've added the IP address and server name to the hosts file and added both to the proxy bypass list. I can browse to the endpoint and view the WSDL in IE and VS's web browser. I can even view the WSDL in the Add Web Reference dialog box in VS. In each case, I'm prompted to select which certificate to use, which I do.
I do not have access to the web service itself or the server it is located on.
I've spent many hours on Google, but have not been able to find a resolution. Any ideas?
Worked around the issue by downloading the WSDL and pulling it into VS through the Add Web Reference dialog by referencing the URL file:\\\drive:\pathname\filename.wsdl.