WSO2 Identity Server web console not responding - wso2-identity-server

I installed WSO2 Identity Server on Ubuntu 14, and I could log in to the web console and dashboard. I recently changed some settings with regards to the system not referring back to 'localhost' so that we could access the system remotely. This all seemed to be working ok.
But now I cannot access the console or dashboard any more. I have checked that the WSO2 service is running, but the web console does not display, it just times out.
The question I have is, how can I troubleshoot this issue? As I don't really want to have to re-install from scratch when I have already done so much configuring!
Any help on this would be very much appreciated!

Related

API calls using postman causing issues

Can someone please help me fixing the Postman Desktop agent issues.
When I try to send a request using postman web, where the send button disabled and saying that to install Desktop Agent.
I have already installed Desktop Agent and it's running. Also, I've changed the postman agent to desktop from the bottom of the postman web(using play button)
But still i'm unable to make api calls and the send button still disabled and saying to install desktop agent.
I've even tried multiple times restarting my laptop, uninstall and re-installing postman desktop agent.
Note - i'm unable to use cloud agent, as i'm sending https requests to my local node application and it's on organizational asset.

WSO2 try it function doesn't work

I installed wso2 api manager and i changed db from internal h2 db to an external MySql database.
I note that when i click on try it option wso2 console shows me a blank tab.
Has someone got my problem?
Thanks
Stefano
I solved the problem. It depends of apache web server placed in front of che backend api-manager server.
When I click on "try it" tab the api manager try to load the context "/registry" that i didn't define in web server before.
Now all works correctly.
Thanks
Stefano

Unable to login to WSO AppFactory

WSO2 experts
I downloaded the WSO2 AppFactory, but couldn't login into the web console with admin/admin. Has the default password changed?
Regards,
Terry
Please try with the following credentials
Username:admin#admin.com
password:admin
If you just tried with a downloaded 'binary' set-up of WSO2 App Factory; this will only allow you to log in to the Carbon admin console of the App Factory (If you just clicked on and visited the URL, that was printed on the server console). This Carbon admin console does not have any App Factory specific functionality which you might expect [WSO2 Carbon is the underlying platform which is used by all of the WSO2 products].
Since App Factory runs having few other servers alongside (such as WSO2 AS, WSO2 ELB, Jenkins, Redmine etc) this set up that you are running will not provide the same User interfaces or functionality which you have observed within the setup provided with https://appfactorypreview.wso2.com/samlsso .
I just thought to leave this answer, because; you would get disappointed after spending your time expecting the same Application (User Interfaces) available with the online setup (which I have mentioned with the hyperlink) by running the binary setup(wso2appfactory-1.0.0.zip) that you have downloaded from the WSO2 Web site.

SharePoint Web Services, Access Denied, Authentication Issues via VS 2010

After not getting much help on the last question, I decided to blow away the VM and re-create it as I already lost a week on this issue. And of course still issues, btu a little different.
I am using WSS on a 2008 server. I removed from the SharePoint admin the blocked asmx page types. I am using the administrator account with password and the domain, which is the IP of the VM machine. Normally I would never recommend using the admin account, but since I am just running a test to connect to SharePoint web services, so be it.
When accessing this site via a webbrowser, no issues whatsoever.
When accessing the web services from the browser using the admin credentials, no problem.
Then when trying to access the web service via Visual Studio I get the windows security dialog;
Followed by a discovery credential for the list;
Followed by another Discovery Credential for access to the error.aspx page, but as you can see, I can see the list of services for lists.asmx;
Followed by yet another Discovery Credential asking for permission to the $metadata and this just continues continually -it will NEVER authenticate via visual studio 2010;
And then, of course, when the code is ran, what do we get - ACCESS DENIED.
Call made; code not listed makes connection.
Make call to service:
And receive the error.
And IIS for SharePoint is set top Windows Authentication and Impersonate. All defaults.
It has now been going on 5 days; does anyone at all have any clue as to what is causing this? I have used this code and technique for years with Windows Server 2003 and WSS 2.0 and / or MOSS 2007 connecting from remote machines and NEVER, I mean NEVER had issues like this.
I would really appreciate any help.

installing an XML Websevice on Windows7 home basic

i've searched the site for this answer but couldnt find a good answer.
My client has a computer with Windows7 Home Basic Installed in his workstation (Thank you HP).
and i need to install a web service on IIS. Web service is written in c# (.asmx). When i installed IIS into that windows, i've realized that there is no IIS comsole available in windows7 home basic machines.
is there a way to register web service from the command prompt? this web service is a middleware for communication several mobile devices with the sql server on the machine so it has to be able to connect form outer ip's too.
I've tried IISExpress but it only lets connectiong from localhost.
I cannot format his harddisk, also my client doesnt really want an edition upgrade.
Thanks for spending your time.
I did a quick google search on hosting a web service (*.asmx) without IIS, and found this article: Run ASMX Without IIS. A quick glance at it looks like you'd wind up writing your own host and implementing your own web server.
If this is the only solution available, I think you'd be far better off to rewrite your ASMX web service as a WCF web service, and then either self-host it or host it in a Windows Service.