Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menunjukkan cara menyelesaikan masalah terkait origin
saat Anda mengonfigurasinya agar berfungsi dengan Media CDN.
Memecahkan masalah konektivitas origin
Jika Anda menerima error HTTP 50x, seperti HTTP 502 (Waktu Tunggu Gateway) atau HTTP
500 (Error Server Internal), pertimbangkan hal berikut:
Uji apakah nama host asal dapat di-resolve dengan Google Public DNS, dan apakah alamat IP yang di-resolve cocok dengan ekspektasi. Jika Anda baru-baru ini mengubah data DNS, resolver mungkin
masih memiliki alamat lama di cache-nya.
Jika origin Anda hanya mendukung HTTP/1.1 dan tidak mendukung HTTP/2,
konfigurasi kolom protocol di origin untuk menggunakan HTTP atau HTTPS,
bukan HTTP2. CDN Media tidak kembali ke koneksi HTTP/1.1 kecuali jika ditentukan.
Pastikan origin memiliki sertifikat SSL (TLS) yang valid (tepercaya secara publik) dan belum habis masa berlakunya.
Trailer HTTP/2 tidak didukung, dan permintaan ke server origin
tidak menyertakan header permintaan "TE". Cuplikan yang disertakan dalam
respons tidak di-cache atau ditampilkan ke klien.
Memecahkan masalah failover origin
Jika failover origin tidak berperilaku seperti yang diharapkan, pertimbangkan hal berikut:
Pastikan penulisan ulang header host yang sesuai dikonfigurasi di origin penggantian Anda.
Pastikan origin utama Anda dikonfigurasi dengan maxAttemptsTimeout, maxAttempts, dan timeouts yang memadai untuk mengakomodasi pengalihan dan failover origin. Pengalihan origin dihitung sebagai upaya koneksi
terpisah terhadap setelan maxAttempts.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[],[],null,["# Troubleshoot origins\n\nThis page shows you how to resolve issues with [origins](/media-cdn/docs/origins)\nwhen you configure them to work with Media CDN.\n\nTroubleshoot origin connectivity\n--------------------------------\n\nIf you are receiving HTTP 50x errors, such as HTTP 502 (Gateway Timeout) or HTTP\n500 (Internal Server Error), consider the following:\n\n- Test that the origin hostname can be resolved with [Google Public\n DNS](http://dns.google.com/), and that the resolved IP addresses matches\n expectations. If you recently changed your DNS records, resolvers might\n still have the old address in their caches.\n\n- If your origin *only* supports HTTP/1.1 and does not support HTTP/2,\n configure the `protocol` field on the origin to use `HTTP` or `HTTPS`\n instead of `HTTP2`. Media CDN does not fall back to HTTP/1.1\n connections unless specified.\n\n- Check that [request logs in Cloud Logging](/media-cdn/docs/logging)\n contain the correct origin IP address.\n\n- Check that origin has a valid (publicly trusted) and unexpired SSL (TLS)\n certificate.\n\n- HTTP/2 Trailers are not supported, and requests to an origin\n server don't include the \"TE\" request header. Trailers included in a\n response are not cached or returned to the client.\n\nTroubleshooting origin failover\n-------------------------------\n\nIf an origin failover isn't behaving as expected, consider the following:\n\n- Ensure that the appropriate host header rewrite is configured on your\n failover origin.\n\n- Ensure that your primary origin is configured with sufficient\n `maxAttemptsTimeout`, `maxAttempts`, and `timeouts` to accommodate origin\n redirects and failovers. Origin redirects count as separate connection\n attempts against the `maxAttempts` setting.\n\nWhat's next\n-----------\n\n- Read about [origin connectivity and shielding](/media-cdn/docs/origins)"]]
