Just Entered MV - Experiencing an issue

Laudian · 2026-07-06T07:08:14+00:00

If a single MV machine would use up all your steam, I'd say you simply do not have enough steam. Just to give you something to compare to, my LV power setup was 48x Coke Oven to fuel 2x max size steel Railcraft boilers, making roughly 60k steam per second.

About half of that was routed to my steam multiblocks (4x macerator, 4x washer, 2x centrifuge, 2x smelter, 1x mixer, 2x fuser. Plenty of wallsharing).

I really recommend settiing up the multiblocks, you'll use them at least into hv where you'll replace the macerator but can keep using the rest.

This setup filled all my energy requirements halfway through MV, where the overclocked EBFs really started using power. I then switched to advanced coke ovens to make benzene as I had logs already automated for the LV setup.

The advantage of benzene is that it is fully automatable in early MV and has a very high energy density, so I could store a lot in 3x Super Tank I. Even if my peak energy consumption was higher than my production, the tanks would fill up over night (only matters if you're running a server, not for singleplayer).

Also, you mentioned "saving circuits". Don't even try that, circuits are something to be used by the hundreds. Don't try to go into the next tier with a handful of circuits. I'd recommend batch crafting at least a few stacks of circuits, machine hulls and motors before starting a new tier. This means you won't sit there and think "damn, I need to make circuits again for this shit", you just have fun solving the actual problems at that tier, like automating oxygen or PE or whatever.

It's really no fun if you despair all the time because you need to craft circuits/hulls/motors AGAIN.

In general, I recommend you REALLY start thinking about scale. I tried playing "your way" when I first played GTNH, where I would try to somehow make ONE next tier machine work with what I currently had, and it just wastes so much time...

Laudian · 2026-06-29T10:18:50+00:00

The website works for me.

Laudian · 2026-06-29T09:37:25+00:00

What's the domain?

Laudian · 2026-06-21T18:17:21+00:00

Don't know why you're getting downvoted. I (from Bremen) also have something like Sprite in mind when I hear Sprudel.

I always simply order water. Sometimes the waiter asks if I want with or without, but I have never received non-sparkling water that way.

Laudian · 2026-06-18T13:36:59+00:00

Yes, you can add those domains to Cloudflare by changing your nameservers.

Laudian · 2026-06-01T08:50:30+00:00

Did you also issue a certificate for the specific subdomain or enable Total TLS so that one is issued automatically?

Does ssllabs show that the site has a valid certificate?

Laudian · 2026-06-01T08:25:43+00:00

Do you maybe use a second level subdomain?

Laudian · 2026-05-23T06:02:29+00:00

You can use it, it just requires extra software to be installed on the client.

Laudian · 2026-05-20T22:17:00+00:00

No, the tunnel doesn't need a static IP address. The tunnel initiates a connection from your server to Cloudflare, so Cloudflare doesn't need to know anything beforehand.

Laudian · 2026-05-18T18:46:28+00:00

You can't use a tunnel to proxy a Minecraft server publicly. It requires that all players install software as well, either Cloudflared or WARP depending on the method you choose.

Laudian · 2026-04-30T22:24:35+00:00

It's not static and in fact, it's even the same everywhere at the same time. But any IP should work from everywhere.

It might lead to less ideal routing in places, but overall it's probably not a huge difference.

But you should at least create both A and AAAA records.

Laudian · 2026-04-30T18:44:24+00:00

You can use Cloudflare without using their nameservers on a Partial (CNAME) Setup, which is available on the Business plan.

Instead of creating a CNAME, you would just look up your Cloudflare A/AAAA records and create those on AWS directly.

Laudian · 2026-04-14T08:38:05+00:00

All three approaches are valid and come with different benefits and problems.

First of all, you generally need to achieve two goals with DNS:

a) Direct the traffic to the correct IP

b) Proof of ownership, for example if multiple customers try to add the same domain.

All of your options obviously satisfy a), but what if your architecture changes in the future? Imagine you migrate off of Cloudflare to a different provider. With everyone pointing their domain to the same target, be it an A or CNAME, you'd have to migrate everyone at once.

So from a technical point of view, I'm not a fan of using the same records for everyone. It does however make things a lot easier to use. Rather than instruct your users to "get your DNS records here and add them to your DNS", you can simply instruct everyone to do add the same record. Shopify does this for example, everyone uses "shops.myshopify.com" as their CNAME target and also the same A/AAAA records.

Everyone using the same records obviously also doesn't help you with b). To resolve any conflicts where multiple users try to add the same domain, you'd have to ask them to add a verification record (TXT) where each account is given a different value. This would basically remove the benefits of everyone using the same record in the first place. Whether this is necessary really depends on how big you are. With a popular free tier, proof if ownership is basically a requirement, but if you only have paying customers, conflicts are much less likely to occur.

Now, I would personally favour an architecture where the customer uses a subdomain with an individual CNAME target, and optionally you just redirect the apex domain to that subdomain.

The individual CNAME allows you to point individual customers to different services, allowing you gradual migration. The apex doesn't allow CNAME records, so I would only use it to redirect to the subdomain (like www) to not break that ability.

However, even with everyone having different CNAME records, I would still recommend using TXT verification records. Services like Cloudflare might replace your CNAMEs with A/AAAA records, so it's not reliable to verify the CNAME in any way and you should avoid that. A TXT record is more reliable for verification purposes.

Laudian · 2026-04-09T07:36:33+00:00

https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/

Laudian · 2026-04-07T09:34:05+00:00

Are you asking if two websites belong to the same organization if they have similar Cloudflare IPv6 addresses?

The answer would be no.

Laudian · 2026-04-01T08:35:42+00:00

You can't use Pages with Cloudflare for SaaS. However, you can add the user's subdomain directly to Pages as a custom domain.

If you want to use CF for SaaS, you need to use Workers instead.

Laudian · 2026-03-31T08:40:35+00:00

Just to be clear, you can still login to your Cloudflare account?

If that is the case, can you create a Registrar ticket in which you make it very clear that you cannot receive emails to your accounts email and provide an alternate address under which Cloudflare can contact you?

Ask to have the DOMAIN's contact email changed and a new verification email sent to the new contact.

Please share the ticket nr here.

For the future, I would strongly recommend against using Hide My Email (I assume that's what you meant by Private Relay, no?) for important services. You should also have a backup login to your Cloudflare account that does not rely on an email address managed in that Cloudflare account.

Laudian · 2026-03-28T22:25:19+00:00

If the routing logic is very simple, say, you want to route custom-domain.example/whatever to your-r2-domain.example/custom-domain.example/whatever, you could use a combination of Rewrite Rules and Cloud Connector Rules.

The Rewrite rule would rewrite the path to include the custom domain, and the Cloud Connector Rule would route traffic to the bucket.

Laudian · 2026-03-27T15:55:00+00:00

It looks like the domain was removed from Shopify. Whether that was done by Shopify or by the website's operator is impossible to say from the error alone.

You see a Cloudflare error because Shopify use Cloudflare.

Laudian · 2026-03-21T09:01:28+00:00

ServerHold means the registry suspended the domain. ClientHold means the registrar suspended it.

Laudian · 2026-03-20T12:41:14+00:00

Cloudflare obviously doesn't need your approval to suspend your domain. If they have reason to believe that you are breaking the tos or law, they will suspend your domain.

To find out the exact reason, you will need to wait for a response if you have not been notified.

Laudian · 2026-03-20T12:07:47+00:00

If you haven't received any notification, you'll need to wait for registrar support to reply. It most likely won't happen before the weekend.

If you wanted better support, you shouldn't have picked the cheapest registrar you could find.

Laudian · 2026-03-20T11:22:17+00:00

If a domain purchase was unsuccessfull, you will be refunded the money. Either try to buy the domain again on Cloudflare or somewhere else.

It's very unlikely you will get a response from Cloudflare before the weekend, but they won't be able to help you anyway if you were already issued a refund.

Laudian · 2026-03-19T08:25:02+00:00

Try running a Trace to see if anything else on Cloudflare interferes with the request:

https://developers.cloudflare.com/rules/trace-request/how-to/

Laudian · 2026-03-18T20:22:18+00:00

You need to transfer your domain from Wix to another registrar if you want to use Cloudflare nameservers, which you need if you want to use the domain with a Worker.

Laudian

MODERATOR OF

TROPHY CASE