Main domain is slow & experiencing downtime but not subdomains? [closed]
Website main domain is constantly going down and up within a span of a few minutes, otherwise it is running slow. This doesn't affect our subdomains. Here is info:
- main domain is slow or down but subdomains aren't affected.
- main domain and subdomain have same code, images etc.
- TTFB for main domain is 45 seconds.
- TTFB for subdomain is 8 seconds.
- both domains use the same database.
- both domains hosted on same server.
From my understanding, if it was a database issue, they'd both be slow due to too many connections. If it was a resource issue, they'd both be slow and experience downtime. We use Plesk + Apache. Can any of you point me in right direction as we haven't found solution? Any ideas?
dns apache-http-server website domain
asked Jan 8 at 17:29
user892134user892134
101
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
closed as too broad by DavidPostill♦ Jan 8 at 20:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
Website main domain is constantly going down and up within a span of a few minutes, otherwise it is running slow. This doesn't affect our subdomains. Here is info:
- main domain is slow or down but subdomains aren't affected.
- main domain and subdomain have same code, images etc.
- TTFB for main domain is 45 seconds.
- TTFB for subdomain is 8 seconds.
- both domains use the same database.
- both domains hosted on same server.
From my understanding, if it was a database issue, they'd both be slow due to too many connections. If it was a resource issue, they'd both be slow and experience downtime. We use Plesk + Apache. Can any of you point me in right direction as we haven't found solution? Any ideas?
dns apache-http-server website domain
asked Jan 8 at 17:29
user892134user892134
101
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
closed as too broad by DavidPostill♦ Jan 8 at 20:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
If it were me and nothing else was obvious, I would use wireshark or tcpdump or fiddler if necessary to inspect the actual connection and network traffic. This will clearly identify WHERE the delay is, then you dig in to the why. Right now you don’t know the “where.” It could be a DNS issue, a network connectivity issue, browser issue, computer issue, or any number of other things.
– Appleoddity
Jan 8 at 17:47
add a comment |
Website main domain is constantly going down and up within a span of a few minutes, otherwise it is running slow. This doesn't affect our subdomains. Here is info:
- main domain is slow or down but subdomains aren't affected.
- main domain and subdomain have same code, images etc.
- TTFB for main domain is 45 seconds.
- TTFB for subdomain is 8 seconds.
- both domains use the same database.
- both domains hosted on same server.
From my understanding, if it was a database issue, they'd both be slow due to too many connections. If it was a resource issue, they'd both be slow and experience downtime. We use Plesk + Apache. Can any of you point me in right direction as we haven't found solution? Any ideas?
dns apache-http-server website domain
asked Jan 8 at 17:29
user892134user892134
101
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Website main domain is constantly going down and up within a span of a few minutes, otherwise it is running slow. This doesn't affect our subdomains. Here is info:
- main domain is slow or down but subdomains aren't affected.
- main domain and subdomain have same code, images etc.
- TTFB for main domain is 45 seconds.
- TTFB for subdomain is 8 seconds.
- both domains use the same database.
- both domains hosted on same server.
From my understanding, if it was a database issue, they'd both be slow due to too many connections. If it was a resource issue, they'd both be slow and experience downtime. We use Plesk + Apache. Can any of you point me in right direction as we haven't found solution? Any ideas?
dns apache-http-server website domain
dns apache-http-server website domain
asked Jan 8 at 17:29
user892134user892134
101
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 8 at 17:29
user892134user892134
101
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 8 at 17:29
user892134user892134
101
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 8 at 17:29
user892134user892134
101
asked Jan 8 at 17:29
user892134user892134
101
101
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user892134 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
closed as too broad by DavidPostill♦ Jan 8 at 20:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by DavidPostill♦ Jan 8 at 20:02
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
If it were me and nothing else was obvious, I would use wireshark or tcpdump or fiddler if necessary to inspect the actual connection and network traffic. This will clearly identify WHERE the delay is, then you dig in to the why. Right now you don’t know the “where.” It could be a DNS issue, a network connectivity issue, browser issue, computer issue, or any number of other things.
– Appleoddity
Jan 8 at 17:47
add a comment |
If it were me and nothing else was obvious, I would use wireshark or tcpdump or fiddler if necessary to inspect the actual connection and network traffic. This will clearly identify WHERE the delay is, then you dig in to the why. Right now you don’t know the “where.” It could be a DNS issue, a network connectivity issue, browser issue, computer issue, or any number of other things.
– Appleoddity
Jan 8 at 17:47
If it were me and nothing else was obvious, I would use wireshark or tcpdump or fiddler if necessary to inspect the actual connection and network traffic. This will clearly identify WHERE the delay is, then you dig in to the why. Right now you don’t know the “where.” It could be a DNS issue, a network connectivity issue, browser issue, computer issue, or any number of other things.
– Appleoddity
Jan 8 at 17:47
If it were me and nothing else was obvious, I would use wireshark or tcpdump or fiddler if necessary to inspect the actual connection and network traffic. This will clearly identify WHERE the delay is, then you dig in to the why. Right now you don’t know the “where.” It could be a DNS issue, a network connectivity issue, browser issue, computer issue, or any number of other things.
– Appleoddity
Jan 8 at 17:47
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
If it were me and nothing else was obvious, I would use wireshark or tcpdump or fiddler if necessary to inspect the actual connection and network traffic. This will clearly identify WHERE the delay is, then you dig in to the why. Right now you don’t know the “where.” It could be a DNS issue, a network connectivity issue, browser issue, computer issue, or any number of other things.
– Appleoddity
Jan 8 at 17:47