It is not easy to have docker services listening on internal and external IPs at the same time The decision if internal or external IP has to be made on a host-by-host basis Access to external IPs is usually granted to specific IPs (for example specific NetCup Machines).

* currently affected hosts (corpex ticket 5771):

• cloud01: internal
• sg01: external
• sandy: external

• QA Attribute Service (http://report-db01.picalike.corpex-kunden.de:31415): has a blocking problem which leads to slack alerts due to time-outs. The error can be ignored, but all other errors should be investigated
• Image Cloud (ic0*): Some cloud provider return a 403/Forbidden, when it is actually 404/Not Found. You can check this by clicking on the link with your browser. If there is an error 'Unable to find image' or 'Illegal file size', it is actually 'Not Found' and can be ignored.
• Image Picker (http://sandy.picalike.corpex-kunden.de:8042): Same as the QA service, only time-out errors can be ignored.