Messages

Yes!

Thank you so much RamSense. It's working now.

Best regards,

Micha

Hi RamSense,

thank you for your reply.

The domain URL is set in the Vaultwarden general settings and there is no security headers in nginx http server set.





Any further ideas?

Best regards,

Micha

Hello everyone,

I have a self-hosted Vaultwarden instance. After an update, its diagnostics display the following error message:

HTTP Response validation Error
2FA Connector calls:
Header: 'cross-origin-resource-policy' is missing!

On my OPNsense (25.1) system, I'm running the NGINX Plugin (version 1.34_6) as a reverse proxy.
What do I need to configure to eliminate this error message?

I appreciate any suggestions or help.

Best regards,
Michael

Hallo zusammen,

ich habe einen self hosted Vaultwarden. Nach einem Update zeigt mir dieser in der Diagnose folgende Fehlermeldung:

HTTP Response validation Error
2FA Connector calls:
Header: 'cross-origin-resource-policy' is missing!



Auf der OPNsense (25.1) habe ich als Reverse Proxy das NGINX Plugin (Version 1.34_6) am laufen.
Was muss ich hier konfigurieren, damit ich diese Fehlermeldung nicht mehr bekomme.

Bin dankbar für jeden Hinweis / jede Hilfe.

Beste Grüße

Michael

I switched back to 24.7.6 (thanks to ZFS snapshots  ;D) and ngix is working fine now.

So I think in my case it is better to wait for the next version 24.7.9  ;)

After updating to 24.7.8 I have a problem with nginx.

When I want to add a new location, an error message appears. There is also NO entry in the log.

Does anyone have an idea what the problem could be?
It always worked before. It doesn't matter whether something is configured in the location or not. This error message appears.

Add new Location:


The error message:


Thanks in advance .

Micha

Hi,

can anyone recommend a Protectli Vault model (4 ports should be enough)?
It is important that WireGuard runs very efficiently. Fiber 300Mbit down / 150 MBit up.

Other services that should still run: VLAN, NGINX, ACME, OPNvpn and possibly Zenarmor in the future.

Is the V1410 the right device?
Or rather the VP2420 with 16 GB RAM?

Thank you in advance.

Regards,

Micha

[Plugin was merged into OPNsense Plugins, I won't post in this thread anymore.]

Plugin was merged into OPNsense Plugins, I won't post in this thread anymore.
https://github.com/opnsense/plugins/pull/3840

- More DNS Providers added: netlify, namesilo, njalla, vercel, googleclouddns, alidns, powerdns, tencentcloud, dinahosting, metaname, hexonet, ddnss, linode, mailinabox, ovh, namecheap, azure, openstack-designate.
- More input fields and better documentation added for the DNS Provider API Keys.

Hi.

Is os-caddy working with Strato (DYNDNS) ?

Thank you @Fright.

The problem was really the backend settings from proxmox container.

Hi,

I changed client_max_body_size to 200MB and restarted NGINX.

But the error always appeard.

Request is larger than the maximum file size the server allows

ist gelöst, siehe https://forum.opnsense.org/index.php?topic=37936.0

[upload_max_filesize]

Hello,

how can I change the upload_max_filesize from default 1MB to 100 MB?

Picture upload is not possible with 1MB to Wordpress or ghost.

Hope, anyone can help me.  :)

Best regards,
Michael

[Changed the following:]

I have tweaked a few things. It works now.  :)

Changed the following:
Upstream Server: Port changed to 443
Upstream: TLS Enabled = TRUE
Location: Force HTTS = FALSE

Many thanks for your support @Monviech .
That gave me the decisive food for thought.

Thank you for your help.

The location is always website.example.com (see logfile attached). ???

Do you have any ideas what the problem could be?

[That is my configuration in OPNsense]

Hello,

I have installed the ghost.org system (website, running on Proxmox).

It works very well locally.
IP: 192.168.5.55

Unfortunately I can't get to the page via url. I used NGINX in the OPNsense for this purpose.

That is my configuration in OPNsense

Dynamic DNS:
(works fine) website.example.com

ACME Client:
SSL-Certificate: (works fine), ACME-Status OK website.example.com

Firewall - Rules - WAN:
Protocol: IPv4 TCP
Source: *
Port: *
Destination: WAN address
Port: 80,443  (as ALIAS)
Gateway: *
Schedule: *


I have configured the following in OPNsense - Services - Nginx:

General Settings:
Enable nginx: TRUE

Upstream Server:
Description: Website
Server: 192.168.5.55
Port: 80
Server Priority: 1
Max. Connection: 1000
Max. Failures: 10
Fail Timeout: 900

Upstream:
Description: Website_Pool
Server Entries: Website
Load Ballancing Algo: Weighted Round Robin
Enable TLS (HTTPS): FALSE
nothing more configured on this page

Location
Description: Website_location
URL Pattern: /
Upstream Servers: Website_Pool
Force HTTPS: TRUE
nothing more configured on this page

HTTP Server
HTTP Listen Address: 80
HTTPS Listen Address: 443
Default Server: FALSE
Server Name: website.example.com
Location: Website_location
TLS Certificate: website.example.com (ACME Client)
Client CA Certificate: R3 (ACME Client)
Enable Let's Encrypt Plugin Support: TRUE
HTTPS Only: TRUE
nothing more configured on this page

Unfortunately I get an error message when calling https://website.example.com
This page isn't working
website.example.com redirected you too many times.
ERR_TOO_MANY_REDIRECTS

Does anyone have any idea what could be causing this?
Somehow I can't find the error.

Thank you for any advice.

Best regards

Michael