Blazor App - Error: Failed to complete negotiation with the server: Error: Forbidden - asp.net-core

I have a Blazor App that runs perfectly well on localhost, however, when I deploy it to the server I get the following error:
Error: Failed to complete negotiation with the server: Error: Forbidden
Error: Failed to start the connection: Error: Forbidden
Error: Error: Forbidden
Error: Cannot send data if the connection is not in the 'Connected' State.
error comes from blazor.server.js.
I looked everywhere and there is no such error reported as far as I know.

Turns out, firewall was blocking it. Simply changing it's security to a lower level did the trick

Related

Proxy Error: Error reading from remote server

I am fetching a report from my apache including a 41000 rows data report and it gives me following error. I checked the logs and there is no exception there:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /reporting/cards/TransactionHistory_cp_trd_trid1.rpt.
Reason: Error reading from remote server
But when I fetched about 20000 rows, it fetched perfectly.

Puppet agent is not running successfully after updating ssl certs

I am running puppet 3.7. The certs are expiring for me so I have updated the certs (after creating a backup so I am able to get back to the original state and that's fine). After updating the certs on puppetmaster using this, updating certs on the agent using this and updating certs on puppetdb using this, I am unable to run puppet agent successfully on a client box. It gives me the following error:
root#ip-10-181-36:/var/lib/puppet# sudo puppet agent -t
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in 'issue_deprecation_warning')
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Error 403 on SERVER: Forbidden request: newer-generic-host(127.0.0.1) access to /node/ip-10-181-36 [find] authenticated at :39
Error: Could not retrieve catalog from remote server: Error 403 on SERVER: Forbidden request: newer-generic-host(127.0.0.1) access to /catalog/ip-10-181-36 [find] authenticated at :1
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: Error 403 on SERVER: Forbidden request: newer-generic-host(127.0.0.1) access to /report/ip-10-181-36 [save] authenticated at :91
I am stuck at this point and no googling or reading docs or seeing the logs is helping. Does anyone have any ideas?

Getting error "SSL_CTX_use_certificate_file failed" in solaris

I am running a simulator which establishes SSL connections and sends HTTP requests.
But currently when I run the simulator I get below error:
ERROR: SSL_CTX_use_certificate_file failed ERROR: [SSL#906d06c]
error:0906D06C:PEM routines:PEM_read_bio:no start line ERROR:
[SSL#140ad009] error:140AD009:SSL
routines:SSL_CTX_use_certificate_file:PEM lib ERROR: Global SSL
initialization failed
Could anyone help me solve this issue?

WebSocket connection to 'wss://' failed: Unexpected response code: 500

I'm getting 500 error when running SignalR on secure websocket when running on IIS Express.
Site is running on localhost:44300 with default cert.
It works just fine with longPolling.
When changing to webSockets, I'm getting following error:
WebSocket connection to
'wss://localhost:44300/signalr/connect?transport=webSockets&connectionToken='
failed: Unexpected response code: 500
If the error is due to self-signed cert, how do I disable it with SignalR and websockets?
Or could it be caused by something else?
I tried solving this issue with initializing EventMachine, by inserting the following code in an initializer config/initializers/eventmachine.rb:
Thread.new { EventMachine.run } unless EventMachine.reactor_running? && EventMachine.reactor_thread.alive?
and it worked for me!
Maybe check this out:
http://websocketstest.com/
BTW: Internal Error (500)

Getting error when connecting to APNS using PHP

Warning: Invalid argument supplied for foreach() in /home/content/t/3/k/t3kmast3r/html/PushService.php on line 13
Warning: stream_socket_client() [function.stream-socket-client]: unable to connect to ssl://gateway.sandbox.push.apple.com:2195 (Connection refused) in /home/content/t/3/k/t3kmast3r/html/PushService.php on line 53
Failed to connect 111 Connection refused
Fatal error: Call to undefined function socket_close() in /home/content/t/3/k/t3kmast3r/html/PushService.php on line 98
I have godaddy.com's hosting service. Does someone know about godaddy.com support APNS?
The error seems like the destination server "ssl://gateway.sandbox.push.apple.com:2195" rejected your connection. You might want to check with Apple's documentations or contact either GoDaddy, Apple, or both.