Traefik and code 404

[ScreNN]

Hi.

Installed error-pages with traefik today. Everything works fine, but... I have two ports 80 and 443, there is nothing on port 80, but to avoid timeouts and problems with browsers, it is open and redirects everyone to port 443.

If you make a request like http://123.domain.com:443, then error-pages triggers and gives a 404. But if you change the request to https://domain.com:80, then error-pages does not work, but just displays the standard 404 page.

How can I get error-pages to process such requests?

Part of the config

Traefik.yml:

################################################################
#                        EntryPoints                           #
################################################################
entryPoints:
  http:
    address: :80
    http:
      middlewares:
        - error-pages@file
        - ip2location@file
      redirections:
        entryPoint:
          to: https
          scheme: https

  https:
    address: :443
    http:
      middlewares:
        - error-pages@file
        - ip2location@file

Router:

http:
  routers:
    error-pages:
      rule: "HostRegexp(`{host:.+}`)"
      entryPoints:
        - "https"
      service: error-pages
      priority: 10

  services:
    error-pages:
      loadBalancer:
        servers:
          - url: "http://IP:PORT"

Middlewares:

  # Error Pages
    error-pages:
      errors:
        status:
          - "400-599"
        service: error-pages
        query: /{status}.html

[tarampampam]

Hi there! Since the daemon listens to just one port, you need to proxy traffic from one port to another or run a second daemon on the required (second) port.

[ScreNN]

Hi.

Can you elaborate on that? Start another container and create another router with meddlewares with different names?

The thing is that with such bad requests, incomplete information about the client is sent to the traffic log. I have a plugin ip2location, which determines the country of the client. If the request is correct, or for example 403, then everything is fine.

But if the request is bad, I see this in the logs

And I don't understand what country the client came from, because it doesn't transmit country data, with this kind of request. Because he got to a 404, which no one processed.

[ScreNN]

Here's just the right example. I just came across such a client. It is not clear where it came from and where the request was made

[ScreNN]

As an option, some behavior can be solved with a trap router. But in this case the code 503 is transmitted.

Do you think this setting is normal?

Or doesn't it make sense to use a trap router along with error-pages?

Trap Router:

http:
  routers:
    catchall:
      entryPoints:
        - "https"
      # catchall rule
      rule: "PathPrefix(`/`)"
      service: unavailable
      # lowest possible priority
      # evaluated when no other router is matched
      priority: 10

  services:
    # Service that will always answer a 503 Service Unavailable response
    unavailable:
      loadBalancer:
        servers: {}

error-pages Router:

http:
  routers:
    error-pages:
      rule: "HostRegexp(`{host:.+}`)"
      entryPoints:
        - "https"
      service: error-pages
      priority: 1

  services:
    error-pages:
      loadBalancer:
        servers:
          - url: "http://IP:PORT"

EntryPoints:

entryPoints:
  http:
    address: :80
    http:
      redirections:
        entryPoint:
          to: https
          scheme: https

  https:
    address: :443
    http:
      middlewares:
        - error-pages@file
        - ip2location@file

Or just don't look at port 80. There's nothing there anyway.

[ScreNN]

I ran into another problem.

Sometimes my domain is accessed with a subdomain.

subdomain.domain.com

But this page does not exist at my domain
In this case the browser returns a 404. But code-pages does not react to it. Is there any way to fix it?

I tried changing the rule

rule: "HostRegexp("domain.com","{subdomain:[a-z.]+}.domain.com")"