Is there a way I don’t have to pay 2 website subscriptions?
What is the current SSL/TLS setting?
Off
What are the steps to reproduce the issue?
I have a web single application. Architectural thing, it made sense to use a single repo.
It is composed by 2 areas:
a user dashboard/settings which lives in a .com domain, for marketing purposes
a presenter of the user’s area, in a short domain, not .com
So, in summary, I have 1 instance of 1 application, which gets accessed by 2 different domains.
Do I have to purchase 2 website protection subscriptions, or is there a bundle or alias situation?
Sorry for the confusion, the form to submit messages is confusing and that SSL answer was already picked for me, it appeared inavertedely.
I always use full strict SSL, proxied traffic.
My concern is I’ll have an application running in a domain with better protection when accessed from 1 domain, and more basic protection when accessed from other one.
It depends on what you consider “protection” but a paid plan is not necessarily better in this regard. However, if you need the same plan for both domains, you do need to purchase it twice.
List of things the Pro tier has that Free doesn’t:
Defend against common attacks including OWASP vulnerabilities with WAF
Protect against zero-day threats with WAF
Detect and challenge easy-to-detect bots
Prioritized loading of key site assets
Intelligent caching for WordPress
One-click image optimizations
Cache analytics for CDN optimization
I’m not an expert in security, but it seems the first 2 are important for applications with a user authenticated area? (It’s Laravel, not hand-rolled)
Probably this is a rare case, but I feel there should be an “alias” kind of thing, at least cheaper for the 2nd domain - that would have to have exactly the same DNS records.
Yeah, one can dream
It’s a bootstrapped project, and a few dollars matter
Sandro - thank you very much, for the insights and care.