{"id":1822,"date":"2026-07-16T18:15:47","date_gmt":"2026-07-16T15:15:47","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1822"},"modified":"2026-09-11T16:10:30","modified_gmt":"2026-09-11T13:10:30","slug":"smtp-connect-failed-hatasi-wordpress","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/smtp-connect-failed-hatasi-wordpress\/","title":{"rendered":"SMTP connect() failed Hatas\u0131: WordPress’te Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?"},"content":{"rendered":"

WordPress’te e-posta g\u00f6ndermeye \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131zda SMTP connect() failed<\/strong> hatas\u0131 al\u0131yorsan\u0131z, ekranda \u015fu mesaj\u0131 g\u00f6r\u00fcrs\u00fcn\u00fcz:<\/p>\n

SMTP Error: Could not connect to SMTP host.\nSMTP connect() failed.<\/code><\/pre>\n
Bu hata, WordPress’in posta sunucusuna hi\u00e7 ba\u011flanamad\u0131\u011f\u0131 anlam\u0131na gelir. Kimlik do\u011frulama a\u015famas\u0131na bile gelinmemi\u015ftir \u2014 ba\u011flant\u0131 daha kurulamam\u0131\u015ft\u0131r. Bu iyi haber say\u0131l\u0131r, \u00e7\u00fcnk\u00fc sebep s\u0131n\u0131rl\u0131 say\u0131da ve te\u015fhisi h\u0131zl\u0131d\u0131r.<\/p>\n
\n\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. \u00d6nce bunu deneyin<\/a><\/li>\n
  2. SMTP connect() failed ne anlama gelir<\/a><\/li>\n
  3. Neden 1: Port ve \u015fifreleme e\u015fle\u015fmiyor<\/a><\/li>\n
  4. Neden 2: Hosting giden portu engelliyor<\/a><\/li>\n
  5. Neden 3: Sunucu ad\u0131 yanl\u0131\u015f<\/a><\/li>\n
  6. Sunucudan ba\u011flant\u0131 testi<\/a><\/li>\n
  7. SMTP connect() failed \u00e7\u00f6z\u00fcld\u00fc m\u00fc: do\u011frulama<\/a><\/li>\n
  8. AIOWS SMTP Y\u00f6neticisi<\/a><\/li>\n
  9. S\u0131k sorulanlar<\/a><\/li>\n
  10. Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n
    \u00d6nce bunu deneyin<\/h2>\n
    Vakalar\u0131n \u00e7o\u011funda sebep tek bir uyumsuzluktur: port ile \u015fifreleme t\u00fcr\u00fc birbirine uymuyor.<\/p>\n
    SMTP ayarlar\u0131n\u0131za gidin ve \u015fu iki kombinasyondan birini kulland\u0131\u011f\u0131n\u0131zdan emin olun:<\/p>\n
    \n\n\n\n\n\n\n
    Port<\/th>\n\u015eifreleme<\/th>\n<\/tr>\n<\/thead>\n
    587<\/td>\nSTARTTLS<\/td>\n<\/tr>\n
    465<\/td>\nSSL\/TLS<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
    587’ye SSL\/TLS ya da 465’e STARTTLS se\u00e7ilmi\u015fse ba\u011flant\u0131 kurulamaz. Do\u011fru e\u015fle\u015fmeyi se\u00e7ip kaydedin ve test edin.<\/p>\n
    D\u00fczelmezse okumaya devam edin.<\/p>\n
    SMTP connect() failed ne anlama gelir<\/h2>\n
    WordPress e-posta g\u00f6nderirken PHPMailer k\u00fct\u00fcphanesini kullan\u0131r. SMTP yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda PHPMailer \u00f6nce posta sunucusuna bir TCP ba\u011flant\u0131s\u0131 a\u00e7maya \u00e7al\u0131\u015f\u0131r. Bu ad\u0131m ba\u015far\u0131s\u0131z olursa SMTP connect() failed hatas\u0131 d\u00f6ner.<\/p>\n
    Hata genellikle iki alt bi\u00e7imde g\u00f6r\u00fcn\u00fcr ve ikisinin sebebi farkl\u0131d\u0131r.<\/p>\n
    Ba\u011flant\u0131 reddedildi (connection refused).<\/strong> Kar\u015f\u0131 taraf ba\u011flant\u0131y\u0131 aktif olarak geri \u00e7eviriyor. Genellikle o portta dinleyen bir servis yok ya da g\u00fcvenlik duvar\u0131 an\u0131nda kapat\u0131yor. Hata h\u0131zl\u0131 gelir.<\/p>\n
    Zaman a\u015f\u0131m\u0131 (connection timed out).<\/strong> Kar\u015f\u0131 taraf hi\u00e7 cevap vermiyor. Genellikle giden trafik engelleniyor ve paketler sessizce d\u00fc\u015f\u00fcr\u00fcl\u00fcyor. Hata otuz saniye kadar bekledikten sonra gelir.<\/p>\n
    Hatan\u0131n ne kadar s\u00fcrede geldi\u011fi te\u015fhise yard\u0131mc\u0131 olur: an\u0131nda geliyorsa reddediliyor, bekletip geliyorsa engelleniyor.<\/p>\n
    Neden 1: Port ve \u015fifreleme e\u015fle\u015fmiyor<\/h2>\n
    En yayg\u0131n sebep bu ve d\u00fczeltmesi en kolay olan\u0131.<\/p>\n
    587 numaral\u0131 port d\u00fcz ba\u011flant\u0131 olarak a\u00e7\u0131l\u0131r, sonra STARTTLS komutuyla \u015fifrelemeye ge\u00e7ilir. 465 numaral\u0131 port ise ba\u011flant\u0131n\u0131n ilk bayt\u0131ndan itibaren \u015fifrelidir.<\/p>\n
    Bu ikisi kar\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda ne olur: 465’e STARTTLS ile ba\u011flanmaya \u00e7al\u0131\u015f\u0131rsan\u0131z sunucu \u015fifreli veri bekler, siz d\u00fcz metin g\u00f6nderirsiniz, ba\u011flant\u0131 kopar. Tersinde ise sunucu d\u00fcz ba\u011flant\u0131 bekler, siz TLS el s\u0131k\u0131\u015fmas\u0131 ba\u015flat\u0131rs\u0131n\u0131z, yine kopar.<\/p>\n
    Sa\u011flay\u0131c\u0131n\u0131z\u0131n belgeledi\u011fi \u00e7ifti kullan\u0131n. \u0130kisi de destekleniyorsa 587 + STARTTLS daha yayg\u0131nd\u0131r.<\/p>\n
    Neden 2: Hosting giden portu engelliyor<\/h2>\n
    Payla\u015f\u0131ml\u0131 bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131lar\u0131 giden SMTP trafi\u011fini s\u0131n\u0131rlar. 25 numaral\u0131 port neredeyse her zaman kapal\u0131d\u0131r; baz\u0131 sa\u011flay\u0131c\u0131lar 587 ve 465’i de kapat\u0131r.<\/p>\n
    Bu durumda SMTP connect() failed hatas\u0131 zaman a\u015f\u0131m\u0131 bi\u00e7iminde gelir, \u00e7\u00fcnk\u00fc paketler hedefe hi\u00e7 ula\u015fmaz.<\/p>\n
    S\u0131rayla deneyin:<\/strong><\/p>\n
    587 \u00e7al\u0131\u015fm\u0131yorsa 465’i deneyin. Baz\u0131 sa\u011flay\u0131c\u0131lar birini a\u00e7\u0131k, di\u011ferini kapal\u0131 tutar.<\/p>\n
    \u0130kisi de \u00e7al\u0131\u015fm\u0131yorsa 2525 numaral\u0131 portu deneyin. Baz\u0131 i\u015flemsel e-posta sa\u011flay\u0131c\u0131lar\u0131 bu portu alternatif olarak sunar ve bar\u0131nd\u0131rma firmalar\u0131 genellikle engellemez.<\/p>\n
    Hi\u00e7biri \u00e7al\u0131\u015fm\u0131yorsa sa\u011flay\u0131c\u0131n\u0131za yaz\u0131n. Sorulacak soru net: “Sunucudan giden 587 ve 465 numaral\u0131 portlar a\u00e7\u0131k m\u0131, de\u011filse a\u00e7abilir misiniz?”<\/p>\n
    Sa\u011flay\u0131c\u0131 a\u00e7m\u0131yorsa kalan yol, SMTP yerine API \u00fczerinden g\u00f6nderim yapan bir i\u015flemsel e-posta servisi kullanmakt\u0131r. Bu servisler 443 numaral\u0131 port \u00fczerinden \u00e7al\u0131\u015f\u0131r ve o port hi\u00e7bir zaman engellenmez.<\/p>\n
    Neden 3: Sunucu ad\u0131 yanl\u0131\u015f<\/h2>\n
    Daha az g\u00f6r\u00fcl\u00fcr ama g\u00f6zden ka\u00e7mas\u0131 kolayd\u0131r.<\/p>\n
    Yaz\u0131m hatas\u0131.<\/strong> smtp.gmai.com<\/code> gibi bir harf eksikli\u011fi DNS \u00e7\u00f6z\u00fcmlemesini ba\u015far\u0131s\u0131z yapar ve ba\u011flant\u0131 hi\u00e7 denenmez.<\/p>\n
    Yanl\u0131\u015f sunucu.<\/strong> Gelen posta sunucusu (imap.<\/code> ya da pop.<\/code> ile ba\u015flayan) SMTP i\u00e7in kullan\u0131lamaz. G\u00f6nderim i\u00e7in smtp.<\/code> ile ba\u015flayan adres gerekir.<\/p>\n
    Payla\u015f\u0131ml\u0131 hostingte alan ad\u0131 hen\u00fcz yay\u0131lmam\u0131\u015f.<\/strong> mail.alanadiniz.com<\/code> kal\u0131b\u0131n\u0131 kullan\u0131yorsan\u0131z ve alan ad\u0131 yeni ta\u015f\u0131nm\u0131\u015fsa DNS kayd\u0131 hen\u00fcz olu\u015fmam\u0131\u015f olabilir.<\/p>\n
    Sunucudan ba\u011flant\u0131 testi<\/h2>\n
    SSH eri\u015fiminiz varsa, sorunun WordPress’te mi yoksa sunucuda m\u0131 oldu\u011funu tek komutla anlayabilirsiniz.<\/p>\n
    587 i\u00e7in:<\/strong><\/p>\n
    openssl s_client -starttls smtp -connect smtp.gmail.com:587 -crlf<\/code><\/pre>\n
    465 i\u00e7in:<\/strong><\/p>\n
    openssl s_client -connect smtp.gmail.com:465 -crlf<\/code><\/pre>\n
    Sunucu ad\u0131n\u0131 kendi de\u011ferinizle de\u011fi\u015ftirin.<\/p>\n
    \n\n\n\n\n\n\n\n\n
    \u00c7\u0131kt\u0131<\/th>\nAnlam\u0131<\/th>\n<\/tr>\n<\/thead>\n
    220<\/code> ile ba\u015flayan bir kar\u015f\u0131lama sat\u0131r\u0131<\/td>\nBa\u011flant\u0131 kuruldu, sorun WordPress ayarlar\u0131nda<\/td>\n<\/tr>\n
    Connection refused<\/code><\/td>\nO portta dinleyen servis yok, sunucu ad\u0131 veya port yanl\u0131\u015f<\/td>\n<\/tr>\n
    Uzun bekleyip Connection timed out<\/code><\/td>\nGiden port engelleniyor, sa\u011flay\u0131c\u0131n\u0131za sorun<\/td>\n<\/tr>\n
    verify error<\/code> ile ba\u015flayan sat\u0131rlar<\/td>\nSertifika sorunu, ba\u011flant\u0131 yine de kurulmu\u015f olabilir<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
    \u00c7\u0131kmak i\u00e7in QUIT<\/code> yaz\u0131p Enter’a bas\u0131n.<\/p>\n
    SSH eri\u015fiminiz yoksa bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131n\u0131z\u0131n destek ekibinden bu testi yapmas\u0131n\u0131 isteyebilirsiniz.<\/p>\n
    SMTP connect() failed \u00e7\u00f6z\u00fcld\u00fc m\u00fc: do\u011frulama<\/h2>\n
    Hatay\u0131 \u00e7\u00f6zd\u00fc\u011f\u00fcn\u00fcz\u00fc d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z \u00fc\u00e7 kontrol\u00fc de yap\u0131n.<\/p>\n
    \n\n\n\n\n\n\n\n
    Kontrol<\/th>\nBeklenen<\/th>\n<\/tr>\n<\/thead>\n
    Eklentinin test e-postas\u0131<\/td>\nHatas\u0131z g\u00f6nderilir<\/td>\n<\/tr>\n
    Ger\u00e7ek bir olay (form g\u00f6nderimi)<\/td>\nGelen kutusuna d\u00fc\u015fer<\/td>\n<\/tr>\n
    Kasten yanl\u0131\u015f port girin, test edin<\/strong><\/td>\nHata geri gelmeli<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
    \u00dc\u00e7\u00fcnc\u00fcs\u00fc, ba\u011flant\u0131n\u0131n ger\u00e7ekten kuruldu\u011funu kan\u0131tlar. Yanl\u0131\u015f portla test h\u00e2l\u00e2 “ba\u015far\u0131l\u0131” diyorsa eklenti SMTP’yi kullanm\u0131yor, eski g\u00f6nderim yoluna d\u00fc\u015f\u00fcyor demektir. Kontrolden sonra do\u011fru portu geri girin.<\/p>\n
    \n
    AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/p>\n
    AIOWS SMTP Y\u00f6neticisi<\/h2>\n
    AIOWS SMTP Y\u00f6neticisi, yayg\u0131n sa\u011flay\u0131c\u0131lar i\u00e7in sunucu ve port de\u011ferlerini haz\u0131r sunar. Gmail, Outlook ve Office 365, Yahoo, Zoho ile SendGrid, Mailgun, Amazon SES, Brevo, SparkPost ve Postmark gibi i\u015flemsel sa\u011flay\u0131c\u0131lar listeden se\u00e7ilir; port ile \u015fifreleme e\u015fle\u015fmesi do\u011fru olarak gelir, yani bu makalenin birinci nedeni ba\u015ftan ortadan kalkar. Hosting sa\u011flay\u0131c\u0131n\u0131z\u0131n kendi sunucusunu kullan\u0131yorsan\u0131z “\u00d6zel SMTP Sunucusu” se\u00e7ene\u011fiyle de\u011ferleri elle girersiniz.<\/p>\n
    Ba\u011flant\u0131 testi, sunucuyla yap\u0131lan konu\u015fmay\u0131 ad\u0131m ad\u0131m g\u00f6sterir. Ba\u011flant\u0131n\u0131n hangi a\u015famada koptu\u011funu bu d\u00f6k\u00fcmden okursunuz \u2014 yukar\u0131daki openssl<\/code> testinin verdi\u011fi bilgiyi panelden, SSH eri\u015fimi gerekmeden.<\/p>\n
    Gmail ve Microsoft 365 i\u00e7in EasyConnect farkl\u0131 bir yol izler. Normal OAuth kurulumu Google Cloud Console’da proje a\u00e7may\u0131, izin ekran\u0131n\u0131 yap\u0131land\u0131rmay\u0131, kimlik bilgisi \u00fcretmeyi ve y\u00f6nlendirme URI’si tan\u0131mlamay\u0131 gerektirir. EasyConnect’te “Google ile ba\u011flan” d\u00fc\u011fmesine basars\u0131n\u0131z, yetkilendirme ekran\u0131 a\u00e7\u0131l\u0131r, izni verirsiniz ve ba\u011flant\u0131 kurulur. Konsol ad\u0131m\u0131 yoktur. Ayn\u0131 yetkilendirme Yedekleme Y\u00f6neticisi’nde de ge\u00e7erlidir; bir kez ba\u011flad\u0131\u011f\u0131n\u0131z hesap her iki mod\u00fclde kullan\u0131l\u0131r.<\/p>\n
    S\u0131n\u0131rlar\u0131 a\u00e7\u0131k olsun:<\/strong> mod\u00fcl, bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131n\u0131z\u0131n kapatt\u0131\u011f\u0131 bir portu a\u00e7amaz. SMTP connect() failed hatas\u0131 engellenen porttan kaynaklan\u0131yorsa \u00e7\u00f6z\u00fcm sa\u011flay\u0131c\u0131n\u0131zdad\u0131r \u2014 mod\u00fcl size sorunun orada oldu\u011funu g\u00f6sterir, ama d\u00fczeltemez. Sunucu taraf\u0131ndaki g\u00fcvenlik duvar\u0131 kurallar\u0131na da m\u00fcdahale edemez ve alan ad\u0131n\u0131z\u0131n SPF veya DKIM kay\u0131tlar\u0131n\u0131 DNS’e sizin yerinize yazamaz.<\/p>\n
    AIOWS SMTP Y\u00f6neticisi’ni inceleyin<\/a>AIOWS planlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/p>\n<\/section>\n
    S\u0131k sorulanlar<\/h2>\n
    SMTP connect() failed hatas\u0131 \u015fifremin yanl\u0131\u015f oldu\u011fu anlam\u0131na m\u0131 gelir?<\/strong><\/p>\n
    Hay\u0131r. Bu hata ba\u011flant\u0131 kurulamad\u0131\u011f\u0131n\u0131 s\u00f6yler; kimlik do\u011frulama a\u015famas\u0131na hi\u00e7 gelinmemi\u015ftir. \u015eifre hatas\u0131 ayr\u0131 bir mesajla, 535 koduyla gelir.<\/p>\n
    Ayn\u0131 ayarlar ba\u015fka sitede \u00e7al\u0131\u015f\u0131yor, burada \u00e7al\u0131\u015fm\u0131yor. Neden?<\/strong><\/p>\n
    \u0130ki site farkl\u0131 sunucularda bar\u0131nd\u0131r\u0131l\u0131yorsa biri giden portu a\u00e7\u0131k, di\u011feri kapal\u0131 tutuyor olabilir. Sunucudan ba\u011flant\u0131 testi bunu kesinle\u015ftirir.<\/p>\n
    Hata bazen geliyor bazen gelmiyor, bu normal mi?<\/strong><\/p>\n
    De\u011fil. Aral\u0131kl\u0131 hata genellikle h\u0131z s\u0131n\u0131rlamas\u0131 ya da ge\u00e7ici a\u011f sorunu g\u00f6sterir. K\u0131sa s\u00fcrede \u00e7ok say\u0131da e-posta g\u00f6nderiyorsan\u0131z sa\u011flay\u0131c\u0131n\u0131z ba\u011flant\u0131lar\u0131 ge\u00e7ici olarak reddediyor olabilir.<\/p>\n
    Sertifika do\u011frulamas\u0131n\u0131 kapatabilir miyim?<\/strong><\/p>\n
    Kapatmay\u0131n. Bu, ba\u011flant\u0131y\u0131 \u015fifresiz hale getirmez ama araya girme sald\u0131r\u0131lar\u0131na a\u00e7\u0131k b\u0131rak\u0131r. Sertifika hatas\u0131 al\u0131yorsan\u0131z sorun port-\u015fifreleme e\u015fle\u015fmesinde ya da sunucu ad\u0131ndad\u0131r.<\/p>\n
    2525 portu g\u00fcvenli mi?<\/strong><\/p>\n
    Port numaras\u0131 g\u00fcvenli\u011fi belirlemez, \u015fifreleme belirler. 2525 \u00fczerinden STARTTLS kullan\u0131ld\u0131\u011f\u0131nda ba\u011flant\u0131 587 kadar g\u00fcvenlidir.<\/p>\n
    Kaynaklar<\/h2>\n