there are some issues with the port for 1.17.0, I am going to revert
it back to 1.15.2.

On 2025/05/07 03:40, pvpdm email wrote:
> Hello OpenBSD ports team,
> 
> I am using the latest pre-compiled package of anubis (anubis-1.17.0) on my
> machine in order to safeguard my gitea instance, that I reverse proxy using
> caddy, against scraping. The gitea instance is running on a linux machine in
> the same network and is accessible at http://192.168.1.2:3000 over my LAN.
> When trying to place anubis between caddy and the gitea instance using the
> following configurations, the starting anubis page loads, but it gets stuck
> at "Loading..." and doesn't actually proceed to give the hash challenge to
> the client or let them access the service. It is also odd that the
> robots.txt page is served by anubis. The anubis configuration that I am
> using is:
> 
> export BIND=:8923
> export DIFFICULTY=4
> export METRICS_BIND=:9095
> export SERVE_ROBOTS_TXT=1
> export TARGET=http://192.168.1.2:3000
> 
> and the part of the caddy configuration that is important to this issue is:
> 
> domain.name {
> 
>   reverse_proxy localhost:8923 {
>                header_up X-Real-Ip {remote_host}
>                header_up X-Http-Version {http.request.proto}
>        }
> }
> 
> I also want to mention that using basically the same configuration for
> anubis and caddy (changing 192.168.2.1:3000 to localhost:3000 and
> localhost:8923 to 192.168.1.2:8923) and running the anubis instance on the
> linux host, I was able to get anubis and caddy working. Anubis version was
> the same for both systems.
> 
> 
> Here is also the OpenBSD version from sysctl -n kern.version:
> OpenBSD 7.7 (GENERIC.MP) #625: Sun Apr 13 08:30:20 MDT 2025
> deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
> 
> I don't think that I have anything else to add. If you'd like for me to
> provide anything else, even provide a live domain to see the issue in action
> please let me know.  If I made a mistake and there is a maintainer that I
> should have sent this email to instead of the ports team, I apologize.
> 
> 
> Thanks for your time
>