Proxy to existing web-services #71

New Issue

jeppebundsgaard · 2025-12-22T01:20:27Z

jeppebundsgaard commented

2025-12-22 01:20:27 +00:00

I hope it is okay to ask this question here - I cannot find a dedicated support-forum.

I have deployed traefik and bonfire to my server. At the server I was running two other webservices via apache.
Now they are failing.
I have tried to understand the instructions here: https://docs.coopcloud.tech/operators/handbook/#proxying-apps-outside-of-co-op-cloud-with-traefik to create a proxy.
But first I don't understand how to create at file at /etc/traefik/file-providers - it is inside the container, so I cannot just create it.
Instead, I added:

COMPOSE_FILE="$COMPOSE_FILE:../../apache/friendica.dk.yml"

to the .env-file (abra app config <traefik-domain>)

And created this file:

---
version: "3.8"
http:
  routers:
    myservice:
      rule: "Host(`friendica.tld`)"
      service: "myservice"
      entryPoints:
        - web-secure
      tls:
        certResolver: production

  services:
    myservice:
      loadBalancer:
        servers:
          - url: "http://MYIP:8080/

I added version "3.8" to avoid version mismatch.

This give the following error when deploying:

FATA (root) Additional property http is not allowed

I seems to be due to the version of traefik not accepting http-value.
But then, what should I do?

Thanks!

I hope it is okay to ask this question here - I cannot find a dedicated support-forum. I have deployed traefik and bonfire to my server. At the server I was running two other webservices via apache. Now they are failing. I have tried to understand the instructions here: https://docs.coopcloud.tech/operators/handbook/#proxying-apps-outside-of-co-op-cloud-with-traefik to create a proxy. But first I don't understand how to create at file at /etc/traefik/file-providers - it is inside the container, so I cannot just create it. Instead, I added: `COMPOSE_FILE="$COMPOSE_FILE:../../apache/friendica.dk.yml"` to the .env-file (`abra app config <traefik-domain>`) And created this file: ``` --- version: "3.8" http: routers: myservice: rule: "Host(`friendica.tld`)" service: "myservice" entryPoints: - web-secure tls: certResolver: production services: myservice: loadBalancer: servers: - url: "http://MYIP:8080/ ``` I added version "3.8" to avoid version mismatch. This give the following error when deploying: > FATA (root) Additional property http is not allowed I seems to be due to the version of traefik not accepting http-value. But then, what should I do? Thanks!

decentral1se commented

2025-12-23 16:57:25 +00:00

hey @jeppebundsgaard, thanks for raising the issue! I think it should probably have ended up here as it is a more general issue but let's keep it going here for convenience sake.

Those instructions you linked to are for allowing traefik to forward to other services that are not in your swarm setup. It's not instructions for running two web proxies in parallel, that isn't supported unfortunately.

You might have to search online how you can route traffic to docker containers with apache via labels. That is what traefik is doing for automatically. At the moment, you need to make a choice if you stick with apache or move over to traefik. You can't mix them on the same server unfortunately because they both claim port 80 and 443.

This is a bit of an annoying limitation atm because we don't "natively" support other proxies. This is a work in progress, e.g. with Caddy: toolshed/organising#388

Hope this helps and let's document the way out of this because for sure others have raised this before.

hey @jeppebundsgaard, thanks for raising the issue! I think it should probably have ended up [here](https://git.coopcloud.tech/toolshed/organising/issues) as it is a more general issue but let's keep it going here for convenience sake. Those instructions you linked to are for allowing traefik to forward to other services that are not in your swarm setup. It's not instructions for running two web proxies in parallel, that isn't supported unfortunately. You might have to search online how you can route traffic to docker containers with apache via labels. That is what traefik is doing for automatically. At the moment, you need to make a choice if you stick with apache or move over to traefik. You can't mix them on the same server unfortunately because they both claim port 80 and 443. This is a bit of an annoying limitation atm because we don't "natively" support other proxies. This is a work in progress, e.g. with Caddy: https://git.coopcloud.tech/toolshed/organising/issues/388 Hope this helps and let's document the way out of this because for sure others have raised this before.

👍 1

jeppebundsgaard closed this issue

2025-12-23 18:24:44 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/traefik#71