We are getting error response "The requested resource is not available." for all the APIs, Post upgrade from WSO2 APIM 3.2.0 to 4.0.0. Kindly suggest to resolve this issue.
During the upgradation process we did not get any error on wso2carbon.log file.
Related
I am not able host the asp.net core 2.2 web api on windows server 2019 iis 10.
I get HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid. I created self contained deployment and even install url rewrite also. But still i am not able to resolve this error. Please help me resolve this issue
Detailed Error Information:
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \?\F:\Publish\Renault\web.config
Requested URL http://localhost:9095/
Physical Path
Logon Method Not yet determined
Logon User Not yet determined
Finally i got the resolution. After installing ASP.net core 3.1.7 hosting model my problem got resolved.
https://download.visualstudio.microsoft.com/download/pr/21a5322f-cf9c-40e0-af41-4cdf14b3fb17/ff1390906525099bcd6b322279e09938/dotnet-hosting-3.1.7-win.exe
I installed API Manager 3.0.0 and started. But I cannot open https://localhost:9443/publisher/ and dev portal in browser. I am getting the following error
syntaxError: invalid for/in left-hand side index.bundle.js:31:204560
What can I do to make it right?
https://docs.wso2.com/display/AM210/Upgrading+from+the+Previous+Release
I am following this to upgrade WSO2 API-M 2.0.0 to 2.1.0.
My 2.0.0 API-M has custom url configured and https certificates configured to map the url.
If i follow the migration as in the document , Will these things gets automatically migrated? Or will i have to manaully change the url in all the configuration files and also do the changes for https ?
I believe you are referring to [1] which is configuring custom URLs per tenant. If so you do not have to redo these configuration in the registry since the new deployment will be pointing to the same registry database as given in the migration documentation.
The changes done to configuration files in the file system, has to be re done in the APIM 2.1.0 pack. You can do a diff of the file system and do those changes.
The SSL certificates also have to be imported again. As an alternative, you can copy the keystores and truststores to the APIM 2.1.0 from the older version instead.
[]https://docs.wso2.com/display/AM200/Customize+the+API+Store+and+Gateway+URLs
I have configured a Facebook login button using accounts-facebook package a while ago and it was working fine, but suddenly it's broken (its not working on the localhost as well as on the droplet giggorilla.co.uk ). I searched for the problem and as recommended I updated form meteor version 1.3 to 1.4, same for accounts-facebook I upgraded to 1.0.11. I double checked app id and secret key and the Facebook app is currently live and available to the public; however I am using http protocol on the environment server and on live server. This is the problem that I am facing:
Error in OAuth Server: Failed to complete OAuth handshake with Facebook. failed [400] {"error":{"message":"This authorization code has been used.","type":"OAuthException","code":100,"fbtrace_id":"HBMaCroDzQN"}}
packages:
accounts-ui#1.1.9
accounts-facebook#1.0.11
accounts-twitter#1.1.12
accounts-password#1.3.1
the facebook app config
the social services config
mup config
I am trying to setup WSO2 API Manager version 2.
I wanted to send an email for user activation. After going through documentation and blogs I came to know that I need UserInformationRecoveryService.
But when I start my WSO2 API Manager with OSGI console flag to run listAdminServices command, in the list I could not get the name ad url for UserInformationRecoveryService.
Can someone guide me on how to install this service in WSO2 API Manager version 2?
Thanks in advance.
Yes, UserInformationRecoveryService is not included by default in API Manager. You need to install that feature. Please refer this article [1].