Search results

ww2 Post in English, please.

You do not do it by posting the word 'bump'. You do it by adding additional information, additional log files, or an additional description of what you tried in the meantime.

It's all externally loaded content from posts and links, like Gravatars, externally loaded images, etc. The forums have no ads or trackers.

On their forums, XF has shown no interest in handling this yet; there are some requests for it there. We're not going to locally patch XF and maintain that patch against upgrades, if that's what you mean.

There appear to be no options for that.

I have tweaked it a little. Verified members ( >= 10 days && >= 10 posts) can edit their own posts/threads indefinitely. Registered members ( < 10 days || < 10 posts) can do so for 24 hours; until they clear the hurdle, at least. I have had to disable deletion of own posts for now (deletion of...

Let's leave it here, gents.

Late to the show: fixed.

You can also keep the defaults and symlink from there: define(`CERT_DIR', `/etc/mail/certs')dnl define(`confCACERT_PATH', `CERT_DIR')dnl define(`confCACERT', `CERT_DIR/cacert.pem')dnl define(`confSERVER_CERT', `CERT_DIR/host.crt')dnl define(`confSERVER_KEY', `CERT_DIR/host.key')dnl...

Maybe nine if you decide to download the source code and offer help. https://docs.freebsd.org/en/articles/contributing/#ports-contributing

Just link to the live environment of LetsEncrypt from your .mc file: (`CERT_DIR', `/usr/local/etc/letsencrypt/live/your.site.name')dnl define(`confCACERT_PATH', `CERT_DIR')dnl define(`confCACERT', `CERT_DIR/chain.pem')dnl define(`confSERVER_CERT', `CERT_DIR/cert.pem')dnl...

Or else you're looking at a possible jail issue, if you're using those (like https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220550).

Try dig @127.0.0.1 A www.freebsd.org (or, drill if you don't have dig). To me it still looks like nothing is actually picking up DNS requests at localhost.

Run (in a separate session), tcpdump -s 0 -pnli re0 dst port 53 and dst net 208.67.216.0/21 and see whether any DNS requests actually make it out at all. If so, drop the dst port 53 and dst portion of it and see whether it's a two-way street By the way, your dnsmasq process was bound to *:53...

options edns0 is a standard part of the automated setup of the local unbound process. It basically allows resolving to use more modern/advanced options (because unbound supports them).

Either unbound or dnsmasq (indeed, why is that running?) should have complained about port 53 already being bound to.

Sounds like Unbound isn't running, check with sockstat -l4p53 and service local_unbound status.

Apparently your PF captures interesting traffic: https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers (you can find out details by Googling for "EMCON IP Protocol" or "ARGUS IP Protocol", etc.). Other than that, you don't seem to be logging any TCP (IP6) or UDP (IP17). Of course, it all...

https://mariadb.com/kb/en/memory-storage-engine/ maybe?

It's just another anti-bot step, fill in whatever you like and stop overthinking everything.