RelaxedFoX
05/25/2023, 7:54 PMhttps://cdn.discordapp.com/attachments/1111381698035327037/1111381698156965908/Screenshot_2023-05-26-01-22-05-05_4d38fce200f96aeac5e860e739312e76.jpg▾
⟁℟♱⋀🐺
05/25/2023, 9:23 PMdaniel
05/26/2023, 3:11 AMpranjal
05/26/2023, 11:49 AMsalad
05/26/2023, 2:38 PMMaxr1998
05/26/2023, 3:40 PMRicky U
05/26/2023, 6:09 PMChaeMin
05/26/2023, 6:37 PMTeo
05/26/2023, 6:42 PMBrianTheImpaler
05/27/2023, 4:00 AMcloudflared | 2023-05-27T03:22:47Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:8989: connect: connection refused" cfRay=<RAYID>-SEA event=1 ingressRule=1 originService=https://localhost:8989
cloudflared | 2023-05-27T03:22:47Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:8989: connect: connection refused" connIndex=0 dest=https://myapp.mydomain.com/ event=0 ip=198.41.192.47 type=http
Any ideas?DvidPi
05/27/2023, 3:22 PMGhostOperator
05/27/2023, 11:04 PMCORS
) when attempting to access my API from a locally running Next.js app. The API itself is forwarded through Zero Trust Cloudflare Tunneling. I would greatly appreciate any help to solve this issue.
Here's the scenario:
- I have a Next.js app running on my local machine, which needs to communicate with my API.
- Whenever I make requests to the API using the Fetch API within my Next.js app, the network tab in the browser displays a "PreflightMissingAllowOriginHeader" error related to CORS.
- Interestingly, I don't encounter any CORS errors when testing the API using tools like Postman.
Key details about my setup:
- The Next.js app is running locally, not hosted via Cloudflare.
- The API server is separate and is forwarded through Zero Trust Cloudflare Tunneling.
Despite these measures, I'm still experiencing the CORS error when attempting to access the API from my Next.js app.
I suspect there may be some configuration aspect related to Cloudflare or the way Zero Trust Cloudflare Tunneling handles incoming requests that I'm overlooking. I would be grateful for any suggestions, troubleshooting steps, or guidance on resolving this issue. I'm also down for providing any details if needed.
https://cdn.discordapp.com/attachments/1112154295001944174/1112154541966758059/image.png▾
https://cdn.discordapp.com/attachments/1112154295001944174/1112154542260363404/image.png▾
somoni
05/27/2023, 11:54 PMDvidPi
05/28/2023, 10:32 AMType - Name - Content - Proxy Status - TTL
A - bedrock - (my IP) - DNS only - Auto
A - mc - (my IP) - DNS only - Auto
SRV - _minecraft._udp - 0 0 19132 bedrock.domain.example - DNS only - Auto
SRV - _minecraft._tcp - 0 0 25565 mc.domain.example - DNS only - Auto
I made sure that I forwarded the right ports on the right protocolssz
05/28/2023, 12:54 PMSlush
05/28/2023, 2:48 PMhttps://cdn.discordapp.com/attachments/1112392025111793824/1112392025266995210/image.png▾
Klont
05/28/2023, 2:54 PMhttps://cdn.discordapp.com/attachments/1112393536076267561/1112393536348885122/image.png▾
lmtr0
05/28/2023, 7:38 PMjs
const fetchBucketContent = async (path: string, bucket: string): Promise<Response> => {
return fetch(`https://${bucket}${path}`, {
cf: {
cacheEverything: true
}
})
}
However, when I look at the cloudflare analytics, this is the percentage of cahing I'm getting:
I was testing my site with Webpagetest and GT Metrics multiple times, I want webpagetest and GTMetrics to receive the cahced content and not the worker content. How would I go about that?
https://cdn.discordapp.com/attachments/1112464946819780710/1112464947255967744/image.png▾
Randomusername
05/28/2023, 8:45 PMDVD
05/28/2023, 10:45 PMDeveloper Joshua
05/29/2023, 12:32 AM"errorMessage": "HTTPSConnectionPool(host='home.nafzigers.us', port=443): Max retries exceeded with url: /api/alexa/smart_home (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1091)')))",
I don't know what to do! I have tried ever type of SSL/TLS type, all with the SAME error. Any ideas?DanTheGoodman
06/13/2023, 12:04 PMfeugnis
07/12/2023, 6:23 PMhighflyingdwarf
08/30/2023, 8:58 PMvoidablemoon884
09/06/2023, 11:25 AMsindrimt
10/27/2023, 9:01 AMBryceWray
11/06/2023, 12:26 PMgeneral-discussions
channel isn’t where to report this, so will try here. (Tag choices didn’t really apply.) Re the Cloudflare Fonts beta: I created a mini-site to test how CFF handles Google’s Latin-language variable serif and sans-serif fonts that have italic styles. The ones which CFF currently doesn’t process correctly are the following, with links provided as examples:
- Brygada 1918 (https://cfftest.brycewray.com/cff003/)
- Noto Serif (https://cfftest.brycewray.com/cff009/)
- Source Serif 4 (https://cfftest.brycewray.com/cff014/)
- DM Sans (https://cfftest.brycewray.com/cff022/)
- Exo 2 (https://cfftest.brycewray.com/cff024/)
- Kumbh Sans (https://cfftest.brycewray.com/cff033/)
- Roboto Condensed (https://cfftest.brycewray.com/cff042/)
- Source Sans 3 (https://cfftest.brycewray.com/cff047/)
To be fair, these amount to a small percentage of the fonts I tested! Good job, CFF team! However, some of these are fairly popular choices and, thus, could merit some attention as to why CFF isn’t processing them yet. Thanks.
*One thing to note for any other user finding this: where a font has a multi-word name, it’s important to make sure your website feeds the necessary link
with an unescaped +
between the font name’s words (e.g., Noto+Sans+Display
for the Noto Sans Display font). I got help with that in the Hugo Discourse (https://discourse.gohugo.io/t/how-to-unescape-plus-sign-in-url-re-cloudflare-fonts/46734) but, if you’re using a different web-building tool, make sure it’s not escaping the +
as &43#;
since that appears to complicate things for CF Fonts.*lky8150
11/10/2023, 12:49 AMjwalker7574
11/11/2023, 9:24 PMdaven_official
11/14/2023, 11:55 PM