Sudden 521 for subdomain

Dear Community,

i’m running my website mydomain(dot)com on Cloudflare with the Setting SSL Full.
I’m also using a service called cloudapp that I have set with a custom url share.mydomain(dot)com that worked always fine.

For one day now however the share.mydomain(dot)com throws a 521 error

My cloudflare setting for this is a CNAME record with share that points to custom.getcloudapp(dot)com as suggested and always worked. I also deleted this record, proxied it, tried SSL flexible, deleted the cloudflare cache, etc.

Nothing so far worked! the normal website mydomain(dot)com works just fine with ssl and everything. The share.mydomain(dot)com

I have a folder /share on my server that I can call with I have an .htaccess script running to have the share.mydomain(dot)com also point to this directory and this always worked.

Any ideas?

If you set it to :grey: in DNS, does it work?

1 Like

This is what I have right now …

If I set it to DNS Only (and not proxied) … This site can’t be reached (ERR_CONNECTION_REFUSED)

But … this happens now with proxied and normal.

Well…that certainly explains the 521. Your server isn’t working.

1 Like

Ok, how so, from today on? As the mydomain(dot)com is normally up and running. Also mydomain(dot)com/share is working normally.

# CLOUDAPP SSL Verification sslforfree
RewriteEngine on
RewriteCond %{HTTP_HOST} ^share\.mydomain\.com$
RewriteCond %{REQUEST_URI} !^/share
RewriteRule ^(.*)$ /share/$1 [L] 
# CLOUDAPP SSL Verification sslforfree

This is what I have in the very first lines of my .htaccess and always had it like that.

What could that mean “the server is not working” for the subdomain, the server is up and running, I can call all urls on the server, just the subdomain is “down”? But the subdomain is a simple subdirectory on the running server right now.

I basically only created this to have an SSL cert installed inside this share directory for Cloudapp links (that I use daily) to also be https.

If you set that hostname to :grey: and it doesn’t work, then there’s something wrong with your server configuration. is a good place to go for help with server configuration problems.

1 Like

Ok, thanks @sdayman. This is super weird though, that it always worked and from today on suddenly stopped working. I’m running this server on an AWS EC2 instance right now.

And you probably stopped that instance. Nothing running at the given hostname, it isnt even pingable →

As @sdayman said, the server isnt working. You need to get it to work, then make sure HTTPS works, and only then proxy it again.

1 Like

Ah, ok, cloudapps service is down. just got it. Thank you.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.