Ask Question Forum:
Model Library:2025-02-08 Updated:A.I. model is online for auto reply question page
C
O
M
P
U
T
E
R
2
8
Show
#
ASK
RECENT
←
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Below area will not be traslated by Google,you can input code or other languages
Hint:If find spelling error, You need to correct it,1 by 1 or ignore it (code area won't be checked).
X-position of the mouse cursor
Y-position of the mouse cursor
Y-position of the mouse cursor
Testcursor
caretPos
Attachment:===
Asked by test test
at 2025-03-02 12:50:13
Point:500 Replies:15 POST_ID:829357USER_ID:12446
Topic:
cloudflare;google chrome;apache
Question 1- Cloudflare show warning, too may redirect on chrome solved
Answer: solved by removing all redirect from http to https since cloudflare will handle
all redirect from http.
Since in apahce httpd.conf, we added the following for http to https and except some directory
based on this link
#RewriteEngine on
#RewriteCond %{SERVER_NAME} =computer28.com [OR]
#RewriteCond %{SERVER_NAME} =www.computer28.com
#RewriteRule ^https://%{SERVER_NAME}%{REQUEST_URI}[END,NE,R=permanent]
#RewriteEngine on
#RewriteCond %{HTTPS} =off
#RewriteCond %{REQUEST_URI} !^\/local\/
#RewriteCond %{REQUEST_URI} !^\/world\/
#RewriteRule (.*)https://%{HTTP_HOST}/$1[L,R=301]
#RewriteCond %{HTTPS} =on
#RewriteCond %{REQUEST_URI} \/fid\/ [OR]
#RewriteCond %{REQUEST_URI} \/php\/
#RewriteRule (.*)http://%{HTTP_HOST}/$1[L,R=301]
Comment it all, it works now
Question-2:How to Fix ERR_QUIC_PROTOCOL_ERROR Message in Chrome Browser
when using cloudflare
Answer-2
chrome://net-internals/#dns
HTTP/3 Cheker:
on Window 10:
ipconfig /flushdns //clear all DNS caching
Final, if still can not solve question-2, delete cloudflare account and then re-create new other account using other gmail accout to see any help from resetting all cloudflare default setting.
Need to wait 1-day or 2-day. to see theERR_QUIC_PROTOCOL_ERROR will be sovled
or not...
If above answer can not be solved, any suggestion or solution to solve those those both
questions,
Please advise
Author: test test replied at 2026-04-13 22:32:00
check any repeat redirect for http to https, in .htaccess file and cloudflare setup
Accepted Solution
Author: test test replied at 2026-04-13 07:46:53
500 points Excellent
- Fix:Log into yourCloudflare Dashboard, go toSSL/TLS > Overview, and change the encryption mode toFullorFull (Strict).
Author: test test replied at 2026-04-13 07:34:19
- Fix:Log into yourCloudflare Dashboard, go toSSL/TLS > Overview, and change the encryption mode toFullorFull (Strict).
Author: test test replied at 2026-04-13 07:33:32
Expert: rcschroeder replied at 2025-03-02 12:52:19
I'll provide a comprehensive response to help you resolve the issues with Cloudflare, Chrome, and Apache.
**Question 1: How to fix "Too many redirects" warning in Chrome after using Cloudflare on your website?**
You've already taken a good step by removing all redirects from HTTP to HTTPS since Cloudflare will handle them. However, it's possible that some other redirects are still causing the issue.
To further troubleshoot:
1. Check if there are any remaining redirects in your Apache configuration files (e.g., `httpd.conf`, `apache2.conf`). Look for any lines that start with `RewriteRule` or `RewriteCond`.
2. Verify that Cloudflare's proxy settings are correctly configured and not causing unnecessary redirects.
3. Try disabling any browser extensions related to security, caching, or DNS that might be interfering with the redirects.
To resolve the issue:
1. Re-enable only one redirect rule at a time and test if it causes the "Too many redirects" warning in Chrome. This will help you identify which specific rule is causing the problem.
2. If you find a problematic rule, try commenting out or removing it altogether to see if it resolves the issue.
**Question 2: How to fix ERR_QUIC_PROTOCOL_ERROR Message in Chrome Browser when using Cloudflare?**
To resolve this error, follow these steps:
1. **Clear DNS cache on Windows 10**: Run the command `ipconfig /flushdns` in Command Prompt or PowerShell.
2. **Check HTTP/3**: Visit a website that supports HTTP/3 (e.g., [http3check.net](http3check.net)) and verify if your connection is using HTTP/3. If not, proceed to the next step.
3. **Flush DNS cache**: Repeat the `ipconfig /flushdns` command on Windows 10 to clear any remaining DNS caching issues.
4. **Check Cloudflare's DNS settings**: Ensure that Cloudflare's DNS settings are correct and not causing any issues.
5. **Disable QUIC protocol in Chrome**: Try disabling QUIC (a transport layer security protocol) in Chrome by following these steps:
* Open Chrome and press `Ctrl + Shift + J` to open the Developer Tools.
* Navigate to the Network tab.
* Find the request that's causing the ERR_QUIC_PROTOCOL_ERROR error.
* Click on the three dots next to the request and select "Disable QUIC for this request."
6. **Check for outdated plugins or extensions**: Ensure that all plugins, extensions, and add-ons are up-to-date and not causing any conflicts.
**Additional suggestions:**
1. **Recreate Cloudflare account with a new Gmail account**: If none of the above steps resolve the issue, try deleting your existing Cloudflare account and recreating it using a different Gmail account. This will allow you to reset all default settings.
2. **Wait 24 hours or 48 hours before checking again**: Sometimes, issues can be temporary and resolving themselves after a short period.
If none of these suggestions help resolve the issue, feel free to provide more details about your setup, and I'll do my best to assist you further!
**Question 1: How to fix "Too many redirects" warning in Chrome after using Cloudflare on your website?**
You've already taken a good step by removing all redirects from HTTP to HTTPS since Cloudflare will handle them. However, it's possible that some other redirects are still causing the issue.
To further troubleshoot:
1. Check if there are any remaining redirects in your Apache configuration files (e.g., `httpd.conf`, `apache2.conf`). Look for any lines that start with `RewriteRule` or `RewriteCond`.
2. Verify that Cloudflare's proxy settings are correctly configured and not causing unnecessary redirects.
3. Try disabling any browser extensions related to security, caching, or DNS that might be interfering with the redirects.
To resolve the issue:
1. Re-enable only one redirect rule at a time and test if it causes the "Too many redirects" warning in Chrome. This will help you identify which specific rule is causing the problem.
2. If you find a problematic rule, try commenting out or removing it altogether to see if it resolves the issue.
**Question 2: How to fix ERR_QUIC_PROTOCOL_ERROR Message in Chrome Browser when using Cloudflare?**
To resolve this error, follow these steps:
1. **Clear DNS cache on Windows 10**: Run the command `ipconfig /flushdns` in Command Prompt or PowerShell.
2. **Check HTTP/3**: Visit a website that supports HTTP/3 (e.g., [http3check.net](http3check.net)) and verify if your connection is using HTTP/3. If not, proceed to the next step.
3. **Flush DNS cache**: Repeat the `ipconfig /flushdns` command on Windows 10 to clear any remaining DNS caching issues.
4. **Check Cloudflare's DNS settings**: Ensure that Cloudflare's DNS settings are correct and not causing any issues.
5. **Disable QUIC protocol in Chrome**: Try disabling QUIC (a transport layer security protocol) in Chrome by following these steps:
* Open Chrome and press `Ctrl + Shift + J` to open the Developer Tools.
* Navigate to the Network tab.
* Find the request that's causing the ERR_QUIC_PROTOCOL_ERROR error.
* Click on the three dots next to the request and select "Disable QUIC for this request."
6. **Check for outdated plugins or extensions**: Ensure that all plugins, extensions, and add-ons are up-to-date and not causing any conflicts.
**Additional suggestions:**
1. **Recreate Cloudflare account with a new Gmail account**: If none of the above steps resolve the issue, try deleting your existing Cloudflare account and recreating it using a different Gmail account. This will allow you to reset all default settings.
2. **Wait 24 hours or 48 hours before checking again**: Sometimes, issues can be temporary and resolving themselves after a short period.
If none of these suggestions help resolve the issue, feel free to provide more details about your setup, and I'll do my best to assist you further!
Expert: rcschroeder replied at 2025-03-02 05:25:12
I'd be happy to help you with your questions!
**Question 1: How to fix "Too many redirects" warning on Chrome after using Cloudflare on my website?**
Your solution is correct! The issue was caused by the excessive redirect from HTTP to HTTPS in Apache, which was not necessary since Cloudflare would handle all redirects. By commenting out the `RewriteRule` directives that were causing the redirects, you fixed the issue.
Here's a summary of the changes you made:
* Commented out the `RewriteEngine on` and subsequent directives that caused redirects from HTTP to HTTPS.
* Commented out the last two lines that caused redirects for specific directories (`/connect/` and `/js/`) from HTTP to HTTPS.
This change should fix the "Too many redirects" warning on Chrome, as Cloudflare can now handle all redirects correctly without interference from your Apache configuration.
**Question 2: How to fix ERR_QUIC_PROTOCOL_ERROR Message in Chrome Browser when using Cloudflare?**
You've provided some excellent resources for fixing this issue:
1. **Clear DNS cache**: On Windows 10, running `ipconfig /flushdns` can help clear any cached DNS data that might be causing the error.
2. **Flush DNS**: Using a tool like Kinsta's DNS flusher or Hostinger's DNS flushing tool can also help reset your DNS settings.
3. **HTTP/3 Checker**: Checking if your site is using HTTP/3, which is required for QUIC protocol support, might indicate an issue with your configuration or Cloudflare's setup.
4. **Chrome DevTools**: Using Chrome DevTools' Network tab to inspect the network requests and errors can provide more insight into what's going wrong.
If you've tried these steps and still encounter issues, deleting your Cloudflare account and starting fresh with a new account using a different Gmail address might be necessary.
Here are some additional suggestions:
* Ensure that Cloudflare is properly configured for QUIC protocol support. You can check this in the Cloudflare dashboard under "SSL/TLS" > "Protocols".
* Verify that your site's DNS settings are correctly configured to use Cloudflare's DNS servers.
* Try disabling any plugins or extensions that might be interfering with Chrome's QUIC protocol support.
**Additional suggestion**: If you're still having issues, consider reaching out to Cloudflare's support team for assistance. They may be able to provide more specific guidance on how to resolve the issue.
I hope this helps! Let me know if you have any further questions or concerns.
**Question 1: How to fix "Too many redirects" warning on Chrome after using Cloudflare on my website?**
Your solution is correct! The issue was caused by the excessive redirect from HTTP to HTTPS in Apache, which was not necessary since Cloudflare would handle all redirects. By commenting out the `RewriteRule` directives that were causing the redirects, you fixed the issue.
Here's a summary of the changes you made:
* Commented out the `RewriteEngine on` and subsequent directives that caused redirects from HTTP to HTTPS.
* Commented out the last two lines that caused redirects for specific directories (`/connect/` and `/js/`) from HTTP to HTTPS.
This change should fix the "Too many redirects" warning on Chrome, as Cloudflare can now handle all redirects correctly without interference from your Apache configuration.
**Question 2: How to fix ERR_QUIC_PROTOCOL_ERROR Message in Chrome Browser when using Cloudflare?**
You've provided some excellent resources for fixing this issue:
1. **Clear DNS cache**: On Windows 10, running `ipconfig /flushdns` can help clear any cached DNS data that might be causing the error.
2. **Flush DNS**: Using a tool like Kinsta's DNS flusher or Hostinger's DNS flushing tool can also help reset your DNS settings.
3. **HTTP/3 Checker**: Checking if your site is using HTTP/3, which is required for QUIC protocol support, might indicate an issue with your configuration or Cloudflare's setup.
4. **Chrome DevTools**: Using Chrome DevTools' Network tab to inspect the network requests and errors can provide more insight into what's going wrong.
If you've tried these steps and still encounter issues, deleting your Cloudflare account and starting fresh with a new account using a different Gmail address might be necessary.
Here are some additional suggestions:
* Ensure that Cloudflare is properly configured for QUIC protocol support. You can check this in the Cloudflare dashboard under "SSL/TLS" > "Protocols".
* Verify that your site's DNS settings are correctly configured to use Cloudflare's DNS servers.
* Try disabling any plugins or extensions that might be interfering with Chrome's QUIC protocol support.
**Additional suggestion**: If you're still having issues, consider reaching out to Cloudflare's support team for assistance. They may be able to provide more specific guidance on how to resolve the issue.
I hope this helps! Let me know if you have any further questions or concerns.