@levelsio Not safe to allow Cloudflare's IP range, as other CF users may query your server, workers etc. (Happened to me few years ago).
No need. just fully isolate the server, and use the CF tunnel to transport the traffic
Best to block all ports, SSH is rarely the main risk. Block all ports using Hetzner's firewall or directly on the server (except temporary your IP on port 22 for ex)
Then, use a Cloudflare Tunnel to securely route traffic from your server to Cloudflare only
The real risk usually comes from reverse proxies or scripts listening on 0.0.0.0, not just SSH. Also, your server shouldn't be reachable on any open port, discoverable, or easily resolvable by scrapers trying to find the IP behind the Cloudflare proxy
Just released In-Editor AI Artistry:
GPT-4o ImageGen in Cursor
Text-to-image & image-to-image (with mask) via MCP server, no extra plugins needed
> https://t.co/4JfxSpn98a
Disputed claims often involve missing or incorrect balances. But “DISPUTED” users were invited too to link Kraken/BitGo. So I expect FTX to add an “Accept Objection” button soon, letting you continue and access your funds.
Disputed claims often involve missing or incorrect balances. But “DISPUTED” users were invited too to link Kraken/BitGo. So I expect FTX to add an “Accept Objection” button soon, letting you continue and access your funds.
Disputed claims often involve missing or incorrect balances. But “DISPUTED” users were invited too to link Kraken/BitGo. So I expect FTX to add an “Accept Objection” button soon, letting you continue and access your funds.
Update about FTX with claim "disputed"
On February 1, 2025, the court released a document addressing an objection to certain customer's claim.
The most likely reason your claim is disputed is detailed in the document. Please locate your claim using CTRL+F and find using a unique token balance you had
https://t.co/4MDdmdWzuh
@sunil_trades
Have 100s of DMs from creditors
Please post comments/replies under tweets instead as difficult for me to answer each DM and most are the same
Many Creditors have Disputed for Claim Status in the FTX Claims
FTX Disputed claims seem tied to incorrect or missing balances. Many “disputed” users have already been invited to link their Kraken/BitGo as the "Allowed" claims
So I suspect FTX will soon add an “Accept the Objection” button so you can proceed or contest and finally access your funds
FTX Claims: Disputed
Find your claim on Kroll
https://t.co/tGq7HDOJEn
1) Advanced Search
2) Search by your Customer ID (Customer Code)
3) Bottom will populate with your FTX claims
4) 1 should be surviving
Should provide reasons for Disputed claim
FTX Claims: Disputed
Find your claim on Kroll
https://t.co/tGq7HDOJEn
1) Advanced Search
2) Search by your Customer ID (Customer Code)
3) Bottom will populate with your FTX claims
4) 1 should be surviving
Should provide reasons for Disputed claim
You should find the reason in the objection document related to your claim, which in most cases is:
"The Debtors have conducted a review of the filed proof of claim and any related accompanying materials and their books and records. Based on this review, the Debtor submits that the customer asserted cryptocurrency quantities and fiat which does not match the quantities and holdings in such customer’s accounts. Accordingly, the Debtors seek to modify the asserted claim to match their books and records."
@LouisOrigny@No_man_one Actually, it's not a KYC issue, based on my observation, it's most likely a mismatch in their recorded balances and the claim
https://t.co/pluAtAag1G
Update about FTX with claim "disputed"
On February 1, 2025, the court released a document addressing an objection to certain customer's claim.
The most likely reason your claim is disputed is detailed in the document. Please locate your claim using CTRL+F and find using a unique token balance you had
https://t.co/4MDdmdWzuh
@sunil_trades
@D7Health There are multiple objection documents, you're probably on a different one.
Check your emails (~February 1, 2025) to find the correct document
@D7Health There are multiple objection documents, you're probably on a different one.
Check your emails (~February 1, 2025) to find the correct document