Redirect cloud.domain.com to other host

Traefik Traefik v2
, ,
1

Hi, quite new to Traefik, migrated V1 to V2 yesterday, that went good.
However I have 1 public IP, and traefik is now running on port 80 and 443.

But I have another server running Nextcloud, on another internal IP.
Now I'd like Traefik to catch the traffic going to cloud.domain.com and forward it to that host omn the internal network.

What would be the best way to implement this?
I've been going through the docs, and a loadbalancer looks like the right option,
specifying the server but I cannot get it to work so far...

The traefik currently runs a few docker containers, and these work great.
Not sure if I should go for a file or tcp thing, but please advice.

Please help

2

Can you post your config? That is usually a good first step in debugging things

3

Currently I have no config to do this, I am a bit fussed about what I should use to achieve this, a router, something else or idk?

4

Hi there,

Config:

traefik.yml

api:
  dashboard: true

entryPoints:
  http:
    address: ":80"
  https:
    address: ":443"

providers:
  docker:
    endpoint: "unix:///var/run/docker.sock"
    exposedByDefault: false
  file:
    directory: traefik_dynamic
certificatesResolvers:
  http:
    acme:
      email: contact@arwingship.nl
      storage: acme.json
      httpChallenge:
        entryPoint: http

traefik_nextcloud.yml inside directory traefic_dynamic:

http:

  routers:
    # Define a connection between requests and services
    to-nextcloud:
      entrypoints:
      - http
      - https
      rule: "Host(`cloud.iwally.nl`)"
      tls:
        certResolver: http
       # If the rule matches, applies the middleware
      # If the rule matches, forward to the whoami service (declared below)
      service: nextcloud

  services:
    nextcloud:
      loadBalancer:
        servers:
          - url: "http://10.15.1.10:80"
5

currently I keep getting error, 404 page not found

6

This was fixed, I needed to enable, insecureSkipVerify: true
as traefik did not see the signed certificate as valid (letsencrypt)