Infos:
- Used Zammad version: latest
- Used Zammad installation type: Under K8s on AWS
- Operating system: aws linux 2
- Browser + version: Brave Latest
Expected behavior:
- Login Screen Zammad
Actual behavior:
- Loading…
Steps to reproduce the behavior:
- up and run zammad latest image on k8s.
The console error from zammad pod:
I, [2021-09-29T01:40:16.495757 #382-180400] INFO – : Started GET “/assets/application-print-5fc8999f1c67c3f71d7daf5227567c6c36fff443806324c6a843e60f679817e0.css” for 10.90.1.37 at 2021-09-29 01:40:16 +0000
I, [2021-09-29T01:40:16.505325 #382-180400] INFO – : Processing by ErrorsController#routing as CSS
I, [2021-09-29T01:40:16.505376 #382-180400] INFO – : Parameters: {“a”=>“assets/application-print-5fc8999f1c67c3f71d7daf5227567c6c36fff443806324c6a843e60f679817e0”}
E, [2021-09-29T01:40:16.508055 #382-180400] ERROR – : No route matches [GET] /assets/application-print-5fc8999f1c67c3f71d7daf5227567c6c36fff443806324c6a843e60f679817e0.css (ActionController::RoutingError)
I, [2021-09-29T01:40:16.508513 #382-180400] INFO – : Rendering inline template
I, [2021-09-29T01:40:16.509039 #382-180400] INFO – : Rendered inline template (Duration: 0.5ms | Allocations: 267)
I, [2021-09-29T01:40:16.511804 #382-180400] INFO – : Completed 404 Not Found in 6ms (Views: 0.8ms | ActiveRecord: 2.1ms | Allocations: 1552)