Solaire
Solaire
Comments
-
Paging VPN addict @Ympker . Yay or nay?
-
Well done! Looks sweet :)
-
Rclone? https://forum.rclone.org/t/make-a-copy-of-folder-on-google-drive-using-rclone/11259
-
Just put "ns1" and "ns2"
-
Wrote a small wrapper around borgbackup that is scheduled by cron (usually between 2 and 3 AM). It consists of dumping all MySQL databases and backing up any folders I configure (usually /var/www and docker volumes). Backups are pushed to a Borg repo on a remote VPS that pushes the backups to my homeserver later that night…
-
https://talk.lowendspirit.com/categories/must-see-deals-/feeds.rss
-
Through the vendor directory according to the WHCMS docs. As this is not a black hat forum as pointed out by @FAT32 we will not write you a tool to exploit this. Every piece of data the user that runs the PHP process can access (and possibly more with the user of other non-WHCMS related exploits), including but not limited…
-
He's likely pointing to the fact that you advertise 5% off using coupon code 10%off.
-
+1 for Backblaze.
-
Nope, it's not used elsewhere :)
-
It shouldn't. Whether you do business with the UK, the USA or even Spain, it's all the same. Reverse charging basically means you give jack shit about how the client pays for his taxes, you're essentially waiving your own liability to do so because you export your service or goods.
-
You keep on reverse charging if it's a business you're trading with. For individuals things have yet to be defined.
-
In the case of a gateway you should be able to open a persistent TCP connection initiates by the gateway and go from there. There's a few solutions already named in this thread that would do exactly that.
-
If you look at protocols like COAP or LWM2M all initiation for connections are done at the client (device) side, simply because of how cellular networks work. Things like updating firmware and application specific configuration is something that should be embedded into your firmware and should be supported by the protocol…
-
It can be fixed but requires modifications to the Vanilla Core which will break future updates. That said, I might have an idea or two on how to solve this without having to modify the Vanilla Core after getting some more experience in working with Vanilla. I've been busy but when I get to it, here's the backlog with items…
-
Paper airplanes. In all seriousness, my phone....
-
I've committed the change to Git :)
-
The first question that popped to mind was actually if whcms is configured to enforce HTTPS but I didn't ask that for no particular reason. :tongue: Since you're using http in your nginx config WHCMS will continously send your browser an http 302, which will change nothing since nginx will still perform a http request…
-
You should remove the trailing slash from the proxy pass directive and add the "host" header. Also, proxy redirect should be set to off and a few other minor things. Try something like this: proxy_pass http://localhost:3000;proxy_redirect off;proxy_set_header Host $host;proxy_set_header X-Real-IP…
-
From the article: Chrome 85 (mid-September 2020) - Google will unify the UA desktop OS string as a common value for desktop browsers. Google will also unify mobile OS/device strings as a similarly common value. They will still be around. They just won't contain your OS anymore and things like that.
-
Parallels is the way to go on Mac to be honest. It's not that expensive and also ships with some cough Linux ISO's cough.
-
For legacy purpose, existing Chrome UA strings will continue to work, so they won't break existing technologies and scripts running across the web. No need to update any code it seems, other than perhaps implementing client hints :)