Whois proxy endpoint error
11 views
Skip to first unread message
Guillaume Blanchet
Feb 27, 2024, 4:17:18 PM2/27/24
to nomulus-discuss
Hello,
Outbound exception caught for channel [id: 0xef997c93, L:/****:30001 ! R:/*****:24239]
io.netty.handler.codec.EncoderException: google.registry.proxy.handler.HttpsRelayServiceHandler$NonOkHttpResponseException: Cannot relay HTTP response status "404 Not Found" in channel [id: 0xef997c93, L:/*****:30001 - R:/*****:24239]:
<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>404 Not Found</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Not Found</h1>
</body></html>
at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:125)
at io.netty.handler.codec.ByteToMessageCodec.write(ByteToMessageCodec.java:108)
at google.registry.proxy.handler.HttpsRelayServiceHandler.write(HttpsRelayServiceHandler.java:202)
at google.registry.proxy.handler.WhoisServiceHandler.write(WhoisServiceHandler.java:64)
However, the query return the right result when I issued it with the registry tool. I a little stuck. Any advice?
I get this error when I tried to issue standard whois query (whois -h whois.{{proxydomain}} fake.example):
Outbound exception caught for channel [id: 0xef997c93, L:/****:30001 ! R:/*****:24239]
io.netty.handler.codec.EncoderException: google.registry.proxy.handler.HttpsRelayServiceHandler$NonOkHttpResponseException: Cannot relay HTTP response status "404 Not Found" in channel [id: 0xef997c93, L:/*****:30001 - R:/*****:24239]:
<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>404 Not Found</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Not Found</h1>
</body></html>
at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:125)
at io.netty.handler.codec.ByteToMessageCodec.write(ByteToMessageCodec.java:108)
at google.registry.proxy.handler.HttpsRelayServiceHandler.write(HttpsRelayServiceHandler.java:202)
at google.registry.proxy.handler.WhoisServiceHandler.write(WhoisServiceHandler.java:64)
However, the query return the right result when I issued it with the registry tool. I a little stuck. Any advice?
Thanks a lot
Guillaume
Lai Jiang
Feb 28, 2024, 9:22:52 AM2/28/24
to Guillaume Blanchet, nomulus-discuss
The fact that you are getting a 404 message back means you reached a server but the path is not recognized.
Make sure that your proxy config is correct, specifically the ones that specify the relay host and path here.
--
NOTE: This is a public discussion list for the Nomulus domain registry project.
---
You received this message because you are subscribed to the Google Groups "nomulus-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nomulus-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nomulus-discuss/6e362f83-a979-4141-9d7a-331f857f9af6n%40googlegroups.com.
Guillaume Blanchet
Feb 28, 2024, 9:37:41 AM2/28/24
to nomulus-discuss
I realize the relay host must be the pub-api and not the default api. That's why. I guess a better default config placeholder would be:
relayHost: pubapi-dot-registry-project-id.appspot.com
relayHost: pubapi-dot-registry-project-id.appspot.com
Lai Jiang
Feb 28, 2024, 10:35:16 AM2/28/24
to Guillaume Blanchet, nomulus-discuss
Yes, you are right. The default config file predates the splitting of pubapi from default.
Feel free to send a PR.
To view this discussion on the web visit https://groups.google.com/d/msgid/nomulus-discuss/c74a2952-06fe-4e41-bf39-6a719e352a35n%40googlegroups.com.
Guillaume Blanchet
Feb 28, 2024, 11:23:59 AM2/28/24
to nomulus-discuss
Ok, I will do one with all my findings. I notice this reference elsewhere too. Plus, I notice the base image used for the proxy is Java11, but the project is compiled with Java17, so I needed to change the base image there also.
Most of the terraform script were not working well due to some changes on the GCP API side. Also there is multiple obsolete reference to bazel and non-existing registry tool command in the documentation. I think the documentation should be rewritten from scratch. I will see what I can do.
Lai Jiang
Feb 28, 2024, 11:32:28 AM2/28/24
to Guillaume Blanchet, nomulus-discuss
That would be really helpful and appreciated!
To view this discussion on the web visit https://groups.google.com/d/msgid/nomulus-discuss/e0fae2cd-41a2-4d73-a015-350d8eceb628n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages