@herken wrote:
Hello,
to be better in my explanation, i need to explain ma infrastructure
I have 5 virtuals servers : Bitwarden, Jira, Confluence, Owncloud and the HAProxy.
I use a DNS with my nas synology (like xxx.synology.me). Actually to have an access to each server, i opened each port on the router except for bitwarden.
Owncloud is configured on HTTPS, Bitwarden too.
Confluence and Jira use the port 9000 and 8080 on HTTP. (Jira and confluence have a context path. /jira and /confluence)Acually, to access to confluence, it’s like this : https://xxx.synology.me:9000/confluence
I would use the port 443 for all server.
https://xxx.synology.me/confluence
https://xxx.synology.me/jira
https://xxx.synology.me/owncloud
https://xxx.synology.me/bitwardenActually, the configuration on Haproxy i tested
frontend www.mysite.com bind *:443 ssl crt /etc/ssl/private/mydomain.pem acl url_bitwarden path_end bitwarden use_backend bitwarden if url_bitwarden acl url_jira path_end jira use_backend jira if url_jira http-request redirect scheme https unless { ssl_fc } default_backend web_servers backend bitwarden balance roundrobin server bitwarden 192.168.0.123:443 check maxconn 20 ssl verify none backend jira balance roundrobin server jira 192.168.0.124:8080/jira check maxconn 20 backend web_servers balance roundrobin server server1 192.168.0.122:443 check maxconn 20 ssl verify none
If i trying to access to https://xxx.synology.me/ => I have the access to owncloud
But https://xxx.synology.me/bitwarden not working
https://xxx.synology.me/jira not working.If i replace this line => (Ip of bitwarden)
backend web_servers
balance roundrobin
server server1 192.168.0.123:443 check maxconn 20 ssl verify noneI accessed at bitwarden. When i use the path_end, it’s not working. Something is wrong…
Can you help me? I hope it’s clear for you
Posts: 1
Participants: 1