I'm using WSO2 IoT Server 3.1.0 Update 5, and I've this problem: the Dashboad not show any data (and if I inspect with the developer with of Chrome, I found a lot of 404 errors)
When I open
- myip:9443/devicemgt/ : Everything is OK.
But, If I open
- myip:9443/portal/dashboard : the dashboard not refresh any data
In the chrome's console I found a lot of HTTP 404
xxx.xxx.xxx.xxx:9443/portal/apis/xmlhttpclient 404 (Not Found)
Any ideas?
Thanks in advance
Portal app was depreciated with IoTS 3.1.0 GA Release and haven't maintained there after. It is not removed totally from product since it does have few internal dependencies. However portal app will completely remove from product with next major release.
Related
I'm using a Microsoft add-in for Powerpoint called 'Web Viewer' (it's just an iframe, you insert a URL, it displays it in the slide).
I inserted a webpage that uses Socket.IO, and I'm seeing it is not able to connect to the server (even the long polling it's falling back on is not working).
Clearly this is not an issue with the add-in: Any ideas what is going on here?
I tested on Mac 10.13.4 (latest) / Powerpoint (16.12, Office 365 Home) (latest).
The same webpage works in an iframe in the latest Chrome, Firefox, Safari, IE11, so I'm thinking something wonky is going on with the embedded (Webkit) browser that Powerpoint is using on Mac.
The general request flow is:
Browser -> AWS ALB (with stickiness enabled) -> Nginx -> Node
UPDATE
Looked into this further, and having tested other pages that use Socket.IO, I think the only difference in their setups and here is the ALB.
Even with stickiness enabled, the load balancer is clearly seen (in the logs) passing traffic between all EC2s. This leads me to believe the cookie they use is either not being set or not being passed with the requests.
First of all, based on this github issue it should be possible to open a websocket.
There might be a problem with using the unsecure ws://. I know that officejs rejects all requests to http:// and forces you to use https:// with a secure certificate. So they might do the same with WebSockets and force you to use wss:// with a valid certificate.
You can test this more easily in Power Point Online with Chrome. The addin is the same but you get much better error logging in the Devtools Console (hit F12). If it's asecurity issue there should be an error message indicating it.
I had the same issue and S.Freederle is correct. Now I'm able to use socket.io via ngrok to create a secure tunnel (HttpS) to connect to my server and emit the data to my client side in office add-in.
There appears to be something wrong with the Google Admin SDK Channel Stop endpoint affecting all the language libraries. At least Node, Ruby and PHP.
I'm having the issue with "directory"…
It should be: https://www.googleapis.com/admin/directory/v1/channels/stop (404)
This works: https://www.googleapis.com/admin/directory_v1/channels/stop
This is generated: https://www.googleapis.com/admin/directory/v1//admin/directory_v1/channels/stop (404)
Someone else if having the problem with "reports"…
Stop watching google push notifications
Ruby library issue…
https://github.com/google/google-api-ruby-client/issues/251
Node client: https://github.com/google/google-api-nodejs-client/blob/1c0407e56e12a05ec8fa7679df19bdd2436969f5/apis/admin/directory_v1.js
Ruby client: https://github.com/google/google-api-ruby-client/blob/41d9d66e8190c8ced331fcc5e156c5123941d713/generated/google/apis/admin_directory_v1/service.rb
PHP client: https://github.com/google/google-api-php-client/blob/da350e19472f5711703a68a77c6df8d1f5ed4fd4/src/Google/Service/Directory.php
Yes, this appears to be a bug in our API serving system that only affects the Admin SDK Directory and Reports APIs. I'm working with the team to find a resolution.
I have a webservice which is hosted on api server and application on app server which have url's like https://webservice.test.com/ for webservice server and https://app.test.com/ for application.
In application we get live data from database using several service we developed on webservice server using CORS http request.
In some service like login we have passed custom header x-auth-token from server.
Above is the screen shot of response we have got in Google Chrome for the request. The Custom header shown in last is available in application when we use it in chrome or Mozilla. The same response we got in Safari too, x-auth-token also available in response when we check in headers but can't able to read it through code.
Finally, after a lot of search i got answer for my problem, Custom headers from CORS http request can be read only in Safari for latest webkit version i.e above 537. I have checked in all safari browser which is above this webkit version will provide me cusom header value. And similarly in chrome if webkit is less than 537 version you can't able to read it.
Maybe this answer on github could helpa bit : https://github.com/angular/angular.js/issues/6254
I am configuring our API Manager, but running into troubles authenticating via OAuth, seems to be an issue with the API Key Manager. I haven't dug into it yet, but does this come with the API Manager (as I have assumed) or is this a separate installation?
I had the same issue when using the wso2 api manager on a Amazon hosted machine, turn out that Thrift was not working correctly because some problem with multicasting and broadcasting.
What I did to get it working was to switch from ThriftClient to WSClient. If you have a huge amount of requests coming in then Thrift is the recommended solution from wso2 but in any "normal" case you will not have any differences between thrift and WS.
Here is how you switch:
Shut down the API Manager
Open up <api manager install dir>\repository\conf\api-manager.xml
Find ThriftClient
Change this to
<KeyValidatorClientType>WSClient</KeyValidatorClientType>
Start the API Manager
You may get some Warnings while starting up but, try it before you jump to the conclusion that it doesn't work.
Hope it helps!
you can use APIM manager product in a distributed setup as keymanger,gateway,store,publisher..but all functionality come in a single distribution.. ..
Go through the documentation for further guides
I was facing the same issue. Everything started when I created my own jks in order to use SSL without a self-signed certificate. I successfully created the jks and changed it in the carbon file. When I started the server, everything seemed ok; but when I used SOAPUI to test an API call, I got this (in the logs of the api manager):
APIAuthenticationHandler API authentication failure due to Unclassified Authentication Failure
I started digging what was the problem by enabling Debug level in the log4j.properties file, and then tried again a tested with SOAPUI and I got:
APISecurityException: Could not connect to <my api ip address> on port 10397
Then, I read the comment of OneMuppet and I checked that file and I found that the Thrift config has a host option, so I uncommented it:
<KeyValidatorClientType>ThriftClient</KeyValidatorClientType>
<ThriftClientPort>10397</ThriftClientPort>
<ThriftClientConnectionTimeOut>10000</ThriftClientConnectionTimeOut>
<ThriftServerPort>10397</ThriftServerPort>
This Line --> <ThriftServerHost>localhost</ThriftServerHost>
<EnableThriftServer>true</EnableThriftServer>
Save, restarted the server and everything start working correctly.
I got the same below issue after my installation, when i try to invoke the api service it is throwing below error:
900900 Unclassified Authentication Failure Error while accessing backend services for API key validation
After some random checks i have seen the axis2.xml file in /repository/conf/axis2 there it is refering a differnt ip's instead. I change these ip's to my local ip and restarted. The issue is resolved now.
I was facing the same issue. when I was trying to setup API Manager as an API Gateway in a different machine as per the steps given here,
https://docs.wso2.com/display/AM250/Publish+through+Multiple+API+Gateways
Once the setup is done and when I am trying to use this gateway URL, I was getting the below response,
{"fault":{"code":900900,"message":"Unclassified Authentication Failure","description":"Error while accessing backend services for API key validation"}}
After changing the KeyValidatorClientType value to WSClient from ThriftClient on the <api manager install dir>\repository\conf\api-manager.xml
It started working fine. And I was able to get the expected response.
If you changed the admin password, then you also have to update the repository/conf/api-manager.xml file with the new password. The 2 places I have changed (so far) are:
<AuthManager>
and
<APIKeyManager>
but there are other admin usernames in that file. No doubt, I'll get to them....
We have an internal portal hosted on a SharePoint web server. There is a separate server for indexing the portal content. I have a custom web application that invokes the SharePoint search web service and it works fine on my development machine. However when I deploy it to the SharePoint web server, I get this message
"The request failed with HTTP status 401: Unauthorized."
If I try to access the web service from the browser (http:///_vti_bin/search.asmx) from the production server, I get the 401 page. But it works fine from the any other machine. This is an internal portal. Any help would be deeply appreciated.
Thank you.
If you get the 401 error when browsing any Sharepoint page from the local machine, try checking out this article or this article (both from support.microsoft.com)
It describes how to disable/work around the loopback check introduced in windows 2003 sp1.