increased 500 error since new routing on ALB

Question

increased 500 error since new routing on ALB

danduk82 opened this issue 7 years ago · 13 comments

I just noticed that since yesterday [1] when the new routing for print was changed to internal ALB, there are now a few 500 errors, which we didn't have before.

I'll check this on Monday.

[1] https://kibana.bgdi.ch/goto/1496a16d4f95cc1d8b38cf753c7d6cf6

danduk82 commented 7 years ago

testing

Answer 1 · 2018-02-26T10:05:55.000Z

@loicgasser ,
as discussed: here is the new target for the multiprint:
vpc-alb-bgdi-${staging}.intra.bgdi.ch
and use the hostname sevice-print.${staging}.bgdi.ch otherwise the routing will not work (hostname based).

Answer 2 · 2018-02-26T10:06:10.000Z

ha, you must use the port 80

Answer 3 · 2018-02-26T10:08:21.000Z

on the ALB?

Answer 4 · 2018-02-26T10:08:53.000Z

I shouldn't have to. 80 is the default port for http.

Answer 5 · 2018-02-26T10:09:29.000Z

yep, this becomes for multiprint:

curl -H "Host: service-print.${staging}.bgdi.ch" vpc-alb-bgdi-${staging}.intra.bgdi.ch/

Answer 6 · 2018-02-26T10:37:53.000Z

I think it's also killing TOD.dev... in the process ;)

Answer 7 · 2018-02-26T12:16:19.000Z

@loicgasser , the new config (no port, but hostname, direct on the ALB) is working fine (AFAIK).

Could you please tag the new image and deploy int?

Answer 8 · 2018-02-26T12:37:52.000Z

it's on int.

Answer 9 · 2018-02-26T12:43:26.000Z

seems all good. Shall I deploy to prod?

Answer 10 · 2018-02-26T12:51:03.000Z

from a routing point of view, it seems good to me too, please go on

Answer 11 · 2018-02-26T12:53:52.000Z

it's on prod

Answer 12 · 2018-02-26T13:19:26.000Z

Good.

…

On Monday, February 26, 2018, Gasser Loïc wrote: it's on prod -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #77 (comment)