Using pact broker with a path

I am trying to get my pact broker working on my environment. I have the broker running in K8S under https://mydomain/pactbroker (image; dius/pactbroker). I am able to send to the broker with the maven plugin (publish). However when I try to verify I get an error; Request to path '/' failed with response 'HTTP/1.1 401 Unauthorized'

Can someone help me out?

   <build>
        <plugins>
            <plugin>
                <groupId>au.com.dius</groupId>
                <artifactId>pact-jvm-provider-maven</artifactId>
                <version>4.0.10</version>
                <configuration>
                    <serviceProviders>
                        <!-- You can define as many as you need, but each must have a unique name -->
                        <serviceProvider>
                            <name>FaqService</name>
                            <protocol>http</protocol>
                            <host>localhost</host>
                            <port>8080</port>

                            <pactBroker>
                                <url>https://mydomain/pactbroker/</url>
                                <authentication>
                                    <scheme>basic</scheme>
                                    <username>user</username>
                                    <password>pass</password>
                                </authentication>
                            </pactBroker>
                        </serviceProvider>
                    </serviceProviders>
                </configuration>
            </plugin>
        </plugins>
    </build>

Added information (Jun 18, 12:52 CET):

When trying to go through the logs it seems it tries to fetch the HAL root information via path "/". However responds with; [WARNING] Could not fetch the root HAL document

When I enable PreEmptive Authentication i can see that ot give a Warning like [WARNING] Using preemptive basic authentication with the pact broker at https://mydomain so without the path.

The issue was with pact. An issue was raised and should be merged to the next release soon (4.1.4)