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

opex-api problem #500

Open
mitakomeow opened this issue Jan 10, 2025 · 1 comment
Open

opex-api problem #500

mitakomeow opened this issue Jan 10, 2025 · 1 comment

Comments

@mitakomeow
Copy link

mitakomeow commented Jan 10, 2025

Hi
I tried many ways to connect to this api but the api response is empty
In this case, I don't know where the setting is missing.
On the server side, directly request curl http://localhost:8094/config/web/v1 and the response is empty
We need your help.

image

image

image

image

@mitakomeow
Copy link
Author

mitakomeow commented Jan 10, 2025

api logs
25-01-09 11:59:17.924 INFO 7 --- [ main] o.s.c.c.s.ConsulServiceRegistry : Registering service with consul: NewService{id='opex-api-8080', name='opex-api', tags=[], address='172.18.0.28', meta={secure=false}, port=8080, enableTagOverride=null, check=Check{script='null', dockerContainerID='null', shell='null', interval='20s', ttl='null', http='http://172.18.0.28:8080/actuator/health', method='null', header={}, tcp='null', timeout='null', deregisterCriticalServiceAfter='null', tlsSkipVerify=null, status='null', grpc='null', grpcUseTLS=null}, checks=null}
2025-01-09 11:59:19.093 INFO 7 --- [ main] co.nilin.opex.api.app.ApiAppKt : Started ApiAppKt in 71.291 seconds (JVM running for 73.723)

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

2 participants
@mitakomeow and others