Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run project in localhost #12

Open
sakibulhasan opened this issue Aug 17, 2016 · 5 comments
Open

Unable to run project in localhost #12

sakibulhasan opened this issue Aug 17, 2016 · 5 comments

Comments

@sakibulhasan
Copy link

sakibulhasan commented Aug 17, 2016

I am trying to run the project at my local machine. I have my local MySQL server up and running in my local machine and here is the link of my config to support my local environment https://github.com/sakibulhasan/spring-cloud-config. I managed to run all 8 applications. Now while Im trying to click on the login link in web-portal it is throwing the following error. It looks like an issue with api-gateway but I have no idea whats the issue is.

error:

Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as a fallback.

Wed Aug 17 09:36:14 EDT 2016
There was an unexpected error (type=Not Found, status=404).
No message available

@wallishuang
Copy link

I have the same problem with this.... any solution???

@sakibulhasan
Copy link
Author

you gotta hit 8765 port which is the port for gateway which redirects to web portal app

@chensean2
Copy link

Hi, shall i know whether this issue has fixed? i have the same problem, when access user/task api via 8765, it is OK. but couldn't access web-portal's htmls, i am a learner on spring microservice, and has no idea, any one can help? thx

@sakibulhasan
Copy link
Author

This is how the app is being setup. You have to use 8765. check the configuration of gateway app.

@anilallewar
Copy link
Contributor

@chensean2 , we have enforced security for all the endpoints (user/task etc) so that they provide response only if there is authenticated OAuth2 access token sent with the request.

When you access the user/task API directly there is no OAuth2 access token specified in the request and hence it would fail with 403 errors.

However when you go through the API gateway, it is configured to authenticate you if OAuth2 access token does not exist. Subsequent requests to the API that go through the API gateway have the OAuth2 token and hence are honoured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants