Messages

1

24.7 Production Series / Re: caddy plugin dns propagation_timeout

« on: August 22, 2024, 01:54:12 pm »

Hey,

i tried with patch and the new update 27.1.2 with os-caddy-1.6.3

"error","ts":"2024-08-21T20:13:27Z","logger":"tls.obtain","msg":"will retry","error":"[sub.domain.de] Obtain: [sub.domain.de] solving challenge: sub.domain.de: [sub.domain.de] authorization failed: HTTP 403 urn:ietf:params:acme:error:unauthorized - Incorrect TXT record "rekord" (and 1 more) found at _acme-challenge.sub.domain.de (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":2,"retrying_in":120,"elapsed":124.751260674,"max_duration":2592000%7D

The disable dont help by netcup. The options with longer propagation where needed. Do you still need more for debug?

with other dns example clouflare its workes, so its looks like its needed the higher value for netcup.

thanks for your work !

2

24.7 Production Series / Re: caddy plugin dns propagation_timeout

« on: August 21, 2024, 01:15:20 pm »

retries yes, but , example netcup need longer propagation time , when not infinity loop.

https://github.com/caddy-dns/netcup

NOTE: You may need to set an unexpectedly high propagation time (≥ 900 seconds) to give the netcup DNS time to propagate the entries! This may be annoying when executing caddy run/start manually but should not be a problem in automated setups. In exceptional cases, 20 minutes may be required. See

can we have this option? to set a propagation time and delay ?

3

24.7 Production Series / Re: caddy plugin dns propagation_timeout

« on: August 21, 2024, 11:15:20 am »

ich habe den patch eingespielt, sehe auch das disable, aber wo kann ich die werte an sich dann mitgeben? zb für netcup 600 oder 900s?

4

24.7 Production Series / caddy plugin dns propagation_timeout

« on: August 20, 2024, 08:40:28 am »

Hey,

How can i set the propagation_timeout and propagation_delay? When i type this keyword sin the fields , i dont see the config parameter in the json file. Example with netcup you need a high propagation_timeout and propagation_delay time.

Its this possible in the gui or must it have set on the cli?


Greets

5

24.1 Legacy Series / squid update 6.9 to 6.10 failed

« on: July 15, 2024, 07:14:20 pm »

hello,

on one sense i can not upgrade squid to 6.10 :

missing files 6.9 license , gplv2, catalog.mk


pkg-static failes rename ...

have anyone the same problem?

6

24.1 Legacy Series / Re: 24.1.9 NAT Reflection

« on: June 19, 2024, 05:10:47 pm »

 its this the same problem , why my 1:1 NAT outbound was deleted? only the rule for the 1:1 was deleted , the other nat outbound rules was not deleted.

7

German - Deutsch / Re: Problem mit 1:1 NAT auf IPv4 in Verbindung mit TCP-Ports

« on: June 19, 2024, 11:40:31 am »

schau mal bitte bei der 1:1 übersicht , bevor du die regel editierst ob dein external network angezeigt wird oder nur in der 1:1 regel?

8

German - Deutsch / Re: Problem mit 1:1 NAT auf IPv4 in Verbindung mit TCP-Ports

« on: June 19, 2024, 11:33:12 am »

bei mir war es der outbound, weil es über eine andere ip auf wan 1:1 umgesetzt wird. diese war nach dem update weg, sodass es nur noch über die normale wan ip raus ging.

9

24.1 Legacy Series / Re: 24.1.9 NAT Reflection

« on: June 19, 2024, 10:49:39 am »

do you mean me? i recover the rules from a backup config file, for the outbound NAT.

10

24.1 Legacy Series / 24.1.9 bgp Port open

« on: June 19, 2024, 10:23:02 am »

 After update to 24.1.9 i ran a port scan, this time a have a open bgp port

179/tcp open  bgp     (open)

i dont the see port on the wan fw rules open?

i dont use bgp .

i have a ip range from a provider. could it be his device what bgp has open, to communicate with his network?

11

24.1 Legacy Series / Re: 24.1.9 NAT Reflection

« on: June 19, 2024, 09:48:59 am »

After update to 24.1.9 1:1 Nat outbound was not working anymore, the outbound rule over a specific ip was deleted.

12

Tutorials and FAQs / Re: Tutorial: Caddy (Reverse Proxy) + Let's Encrypt Certificates + Dynamic DNS

« on: June 04, 2024, 02:57:13 pm »

i have it done, on first look, looks good.

but why are run caddy on root user? should it not www?

root     caddy      56705 8  tcp4   ip:443

13

Tutorials and FAQs / Re: Tutorial: Caddy (Reverse Proxy) + Let's Encrypt Certificates + Dynamic DNS

« on: June 04, 2024, 02:51:49 pm »

nice , i will try.

then i have no conflicts with the nginx plugin , what used port 80/443 on the first wan port?

14

Tutorials and FAQs / Re: Tutorial: Caddy (Reverse Proxy) + Let's Encrypt Certificates + Dynamic DNS

« on: June 04, 2024, 01:47:50 pm »

can i bind caddy on specific interface?

i have two wan interface and run nginx proxy on one. i want use caddy for the second, to test , but i see no options to bind caddy on a specific interface.

15

24.1 Legacy Series / alias excluds not working with domain name

« on: April 19, 2024, 05:07:53 pm »

 when i want a exclude on a host or network alias , it doesnt allowed a domain name. i saw a bugreport but no answer.


when i excluded in a url table , i can a !domain set , but its exclude nothing.

https://github.com/opnsense/core/issues/6548