Skip to main content

IFSCloud was installed in the order of 24.2.2 (Build-home), 24.2.2 (patch), and 24.2.8 (patch), and no errors were found in the log.
However, when I access it, I get the message "503 Service Temporarily Unavailable."

There are several pods with errors. Attach the logs.
  * pod/ingress-ingress-nginx-controller :Many SSL certificate related errors are displayed
  * pod/ifsapp-proxy :CrashLoopBackOff
  * pod/ifsapp-reporting-web-transformer :CrashLoopBackOff
  * 
ifsapp-proxy pod log(excerpt)
---
[    50.773132s]  WARN ThreadId(01) policy:controller{addr=linkerd-policy.ifs-ingress.svc.cluster.local:8090}: linkerd_app_core::control: Failed to resolve control-plane component error=failed SRV and A record lookups: failed to resolve SRV record: no record found for Query { name: Name("linkerd-policy.ifs-ingress.svc.cluster.local."), query_type: SRV, query_class: IN }; failed to resolve A record: no record found for Query { name: Name("linkerd-policy.ifs-ingress.svc.cluster.local."), query_type: AAAA, query_class: IN } error.sources=[failed to resolve A record: no record found for Query { name: Name("linkerd-policy.ifs-ingress.svc.cluster.local."), query_type: AAAA, query_class: IN }, no record found for Query { name: Name("linkerd-policy.ifs-ingress.svc.cluster.local."), query_type: AAAA, query_class: IN }]
[    50.796267s]  WARN ThreadId(01) dst:controller{addr=linkerd-dst-headless.ifs-ingress.svc.cluster.local:8086}: linkerd_app_core::control: Failed to resolve control-plane component error=failed SRV and A record lookups: failed to resolve SRV record: no record found for Query { name: Name("linkerd-dst-headless.ifs-ingress.svc.cluster.local."), query_type: SRV, query_class: IN }; failed to resolve A record: no record found for Query { name: Name("linkerd-dst-headless.ifs-ingress.svc.cluster.local."), query_type: AAAA, query_class: IN } error.sources=[failed to resolve A record: no record found for Query { name: Name("linkerd-dst-headless.ifs-ingress.svc.cluster.local."), query_type: AAAA, query_class: IN }, no record found for Query { name: Name("linkerd-dst-headless.ifs-ingress.svc.cluster.local."), query_type: AAAA, query_class: IN }]
[    51.023160s]  WARN ThreadId(01) watch{port=4191}: linkerd_app_inbound::policy::api: Unexpected policy controller response; retrying with a backoff grpc.status=Deadline expired before operation could complete grpc.message="initial item not received within timeout"
---

Since there is no domain in this environment, Windows accessing the web changes the hosts file and performs name resolution. Therefore, no certificate is set.
It is not currently dual stacked. (I heard that IPv6 is required)
The server has been restarted. The situation remains unchanged.

What other causes could there be? These two are difficult to address, so please let me know if there are any other possible causes.
* No domain and no certificate
* IPv6 is not supported

Thank you for your cooperation.

Did you configure the middleware with a self-signed certificate, or was no certificate used at all?

Thanks for the question.

 

I created MicroK8s using the ifsroot tool. As of now, a self-signed certificate has been created.

There is no TLS certificate because the domain is not prepared.

 

Thanks again,

Accessing the application via an IP address is likely to fail because even with a self-signed certificate, a proper FQDN is required for the Ingress to correctly handle requests. Additionally, only traffic from trusted networks can reach the application. Since your environment currently has no domain, no valid certificate is configured these factors are likely causing the 503 Service Temporarily Unavailable errors. To resolve this, I think it is recommended to use a proper FQDN with correct DNS configuration and install a valid certificate.

Terms & ConditionsCookie settings