{"id":89711,"date":"2020-07-25T13:42:31","date_gmt":"2020-07-25T11:42:31","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/ustanavlivaem-balansirovshhik-nagruzki-haproxy-na-centos"},"modified":"2020-07-25T13:42:31","modified_gmt":"2020-07-25T11:42:31","slug":"ustanavlivaem-balansirovshhik-nagruzki-haproxy-na-centos","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ustanavlivaem-balansirovshhik-nagruzki-haproxy-na-centos","title":{"rendered":"Instalimi i balancuesit t\u00eb ngarkes\u00ebs HAProxy n\u00eb CentOS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><strong><em>P\u00ebrkthimi i artikullit \u00ebsht\u00eb p\u00ebrgatitur para fillimit t\u00eb kursit <noindex><a rel=\"nofollow\" href=\"https:\/\/otus.pw\/KbNT\/\">\u00abAdministratori Linux. Virtualizimi dhe klasterizimi\u00bb<\/a><\/noindex><\/em><\/strong><\/p>\n<p><img decoding=\"async\" alt=\"Instalimi i balancuesit t\u00eb ngarkes\u00ebs HAProxy n\u00eb CentOS\" src=\"\/wp-content\/uploads\/2020\/07\/0383023d85d77710b1120e5b896a8433.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Balancimi i ngarkes\u00ebs \u00ebsht\u00eb nj\u00eb zgjidhje e zakonshme p\u00ebr shkall\u00ebzimin horizontal t\u00eb aplikacioneve web n\u00eb disa hoste, duke ofruar p\u00ebrdoruesve nj\u00eb pik\u00eb t\u00eb vetme qasje n\u00eb sh\u00ebrbim. <noindex><a rel=\"nofollow\" href=\"http:\/\/www.haproxy.org\/\">HAProxy<\/a><\/noindex> \u00ebsht\u00eb nj\u00eb nga programet m\u00eb t\u00eb njohura p\u00ebr balancimin e ngarkes\u00ebs me burim t\u00eb hapur, e cila gjithashtu siguron disponibilitet t\u00eb lart\u00eb dhe funksionalitet t\u00eb proxy.<\/p>\n<p><\/p>\n<p>HAProxy synon t\u00eb optimizoj\u00eb p\u00ebrdorimin e burimeve, maksimizoj\u00eb kapacitetin e kalimit, minimizoj\u00eb koh\u00ebn e p\u00ebrgjigjes dhe t\u00eb shmang\u00eb mbingarkes\u00ebn e \u00e7do burimi t\u00eb vet\u00ebm. Ajo mund t\u00eb instalohet n\u00eb shum\u00eb distribucione t\u00eb Linux-it, si CentOS 8, mbi t\u00eb cilin do t\u00eb ndalojm\u00eb n\u00eb k\u00ebt\u00eb udh\u00ebzues, si dhe n\u00eb sistemet <noindex><a rel=\"nofollow\" href=\"https:\/\/upcloud.com\/community\/tutorials\/haproxy-load-balancer-debian\/\">Debian 8<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"https:\/\/upcloud.com\/community\/tutorials\/haproxy-load-balancer-ubuntu\/\">Ubuntu 16<\/a><\/noindex>.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Instalimi i balancuesit t\u00eb ngarkes\u00ebs HAProxy n\u00eb CentOS\" src=\"\/wp-content\/uploads\/2020\/07\/53bf7d1fa06f06f5d882e573f4984e4f.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>HAProxy \u00ebsht\u00eb ve\u00e7an\u00ebrisht e p\u00ebrshtatshme p\u00ebr website-t me trafik shum\u00eb t\u00eb lart\u00eb dhe prandaj p\u00ebrdoret shpesh p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar besueshm\u00ebrin\u00eb dhe performanc\u00ebn e konfigurimeve t\u00eb sh\u00ebrbimeve web me disa server\u00eb. N\u00eb k\u00ebt\u00eb udh\u00ebzues p\u00ebrshkruhen hapat p\u00ebr t\u00eb konfiguruar HAProxy si nj\u00eb balancues ngarkese n\u00eb nj\u00eb host cloud CentOS 8, i cili m\u00eb pas drejton trafik n\u00eb serverat tuaj web.<\/p>\n<p><\/p>\n<p>Si nj\u00eb kusht thelb\u00ebsor p\u00ebr t\u00eb arritur rezultatet m\u00eb t\u00eb mira, ju duhet t\u00eb keni t\u00eb pakt\u00ebn dy server\u00eb web dhe nj\u00eb server p\u00ebr balancimin e ngarkes\u00ebs. N\u00eb server\u00ebt web duhet t\u00eb jet\u00eb e instaluar s\u00eb paku nj\u00eb sh\u00ebrbim web themelor, si nginx ose httpd, p\u00ebr t\u00eb verifikuar balancimin e ngarkes\u00ebs midis tyre.<\/p>\n<p><\/p>\n<h2 id=\"ustanovka-haproxy-na-centos-8\">Instalimi i HAProxy n\u00eb CentOS 8<\/h2>\n<p><\/p>\n<p>P\u00ebr shkak se HAProxy \u00ebsht\u00eb nj\u00eb aplikacion me burim t\u00eb hapur q\u00eb po zhvillohet shpejt, distribuimi i disponuesh\u00ebm n\u00eb depozitat standarde t\u00eb CentOS-it mund t\u00eb mos jet\u00eb versioni m\u00eb i fundit. P\u00ebr t\u00eb verifikuar versionin aktual, ekzekutoni komand\u00ebn e m\u00ebposhtme:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo yum info haproxy<\/code><\/pre>\n<p><\/p>\n<p>HAProxy gjithmon\u00eb ofron p\u00ebrzgjedhjen e tre versioneve stabile: dy versionet m\u00eb t\u00eb fundit t\u00eb mb\u00ebshtetura dhe nj\u00eb t\u00eb tret\u00eb, m\u00eb t\u00eb vjet\u00ebr, e cila ende merr p\u00ebrdit\u00ebsime kritike. Ju gjithmon\u00eb mund t\u00eb kontrolloni versionin m\u00eb t\u00eb fundit stabil t\u00eb treguar n\u00eb faqen e HAProxy dhe pastaj t\u00eb vendosni se me cilin version d\u00ebshiron t\u00eb punoni.<\/p>\n<p><\/p>\n<p>N\u00eb k\u00ebt\u00eb udh\u00ebzues do t\u00eb instalojm\u00eb versionin m\u00eb t\u00eb fundit stabil 2.0, i cili ende nuk ishte i disponuesh\u00ebm n\u00eb depo standarde n\u00eb momentin e shkrimit t\u00eb udh\u00ebzuesit. Ju nevojitet ta instaloni at\u00eb nga burimi origjinal. Por fillimisht kontrolloni n\u00ebse keni p\u00ebrmbushur kushtet e nevojshme p\u00ebr t\u00eb shkarkuar dhe kompaktuar programin.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo yum install gcc pcre-devel tar make -y<\/code><\/pre>\n<p><\/p>\n<p>Shkarkoni kodin burimor duke p\u00ebrdorur komand\u00ebn m\u00eb posht\u00eb. Mund t\u00eb kontrolloni n\u00ebse ekziston nj\u00eb version m\u00eb i ri n\u00eb dispozicion n\u00eb <noindex><a rel=\"nofollow\" href=\"http:\/\/www.haproxy.org\/#down\">faqja e shkarkimeve t\u00eb HAProxy<\/a><\/noindex>.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">wget http:\/\/www.haproxy.org\/download\/2.0\/src\/haproxy-2.0.7.tar.gz -O ~\/haproxy.tar.gz<\/code><\/pre>\n<p><\/p>\n<p>Pas p\u00ebrfundimit t\u00eb shkarkimit, shfrytezoni skedar\u00ebt me komand\u00ebn e dh\u00ebn\u00eb m\u00eb posht\u00eb:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">tar xzvf ~\/haproxy.tar.gz -C ~\/<\/code><\/pre>\n<p><\/p>\n<p>Shkoni n\u00eb direktorin\u00eb e shfrytezimit t\u00eb kodit burimor:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">cd ~\/haproxy-2.0.7<\/code><\/pre>\n<p><\/p>\n<p>Pastaj, kompaktikoni programin p\u00ebr sistemin tuaj:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">make TARGET=linux-glibc<\/code><\/pre>\n<p><\/p>\n<p>Dhe, p\u00ebrfundimisht, instaloni vet\u00eb HAProxy:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo make install<\/code><\/pre>\n<p><\/p>\n<p>Tani HAProxy \u00ebsht\u00eb instaluar, por p\u00ebr funksionimin e saj k\u00ebrkohen disa manipulime shtes\u00eb. Le t\u00eb vazhdojm\u00eb me konfigurimin e softuerit dhe sh\u00ebrbimeve m\u00eb posht\u00eb.<\/p>\n<p><\/p>\n<h2 id=\"nastroyka-haproxy-pod-vash-server\">Konfigurimi i HAProxy p\u00ebr serverin tuaj<\/h2>\n<p><\/p>\n<p>Tani shtoni k\u00ebto direktori dhe sked\u00eb statistike p\u00ebr regjistrimet HAProxy:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo mkdir -p \/etc\/haproxy\nsudo mkdir -p \/var\/lib\/haproxy \nsudo touch \/var\/lib\/haproxy\/stats<\/code><\/pre>\n<p><\/p>\n<p>Krijoni nj\u00eb lidhje simbolike p\u00ebr skedar\u00ebt binar\u00eb, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mund t\u00eb ekzekutoni komandat HAProxy si p\u00ebrdorues i zakonsh\u00ebm:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo ln -s \/usr\/local\/sbin\/haproxy \/usr\/sbin\/haproxy<\/code><\/pre>\n<p><\/p>\n<p>N\u00ebse d\u00ebshironi t\u00eb shtoni serverin proxy n\u00eb sistem si nj\u00eb sh\u00ebrbim, kopjoni sked\u00ebn haproxy.init nga shembujt n\u00eb katalogun tuaj \/etc\/init.d. Redaktoni lejet e sked\u00ebs q\u00eb skripti t\u00eb ekzekutohet, pastaj rifilloni demonin systemd:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo cp ~\/haproxy-2.0.7\/examples\/haproxy.init \/etc\/init.d\/haproxy\nsudo chmod 755 \/etc\/init.d\/haproxy\nsudo systemctl daemon-reload<\/code><\/pre>\n<p><\/p>\n<p>Ju gjithashtu duhet t\u00eb lejoni sh\u00ebrbimin q\u00eb t\u00eb rifilloj\u00eb automatikisht kur t\u00eb startohet sistemi:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo chkconfig haproxy on<\/code><\/pre>\n<p><\/p>\n<p>P\u00ebr leht\u00ebsi, rekomandohet gjithashtu t\u00eb shtoni nj\u00eb p\u00ebrdorues t\u00eb ri p\u00ebr t\u00eb ekzekutuar HAProxy:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo useradd -r haproxy<\/code><\/pre>\n<p><\/p>\n<p>Pas k\u00ebsaj, mund t\u00eb kontrolloni p\u00ebrs\u00ebri numrin e versionit t\u00eb instaluar duke p\u00ebrdorur komand\u00ebn e m\u00ebposhtme:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">haproxy -v\nHA-Proxy version 2.0.7 2019\/09\/27 - https:\/\/haproxy.org\/<\/code><\/pre>\n<p><\/p>\n<p>N\u00eb rastin ton\u00eb, versioni duhet t\u00eb jet\u00eb 2.0.7, si\u00e7 shikohet n\u00eb shembullin e daljes m\u00eb sip\u00ebr.<\/p>\n<p><\/p>\n<p>N\u00eb fund, firewalli n\u00eb CentOS 8 \u00ebsht\u00eb mjaft restriktiv p\u00ebr k\u00ebt\u00eb projekt. P\u00ebrdorni komandat e m\u00ebposhtme p\u00ebr t\u00eb lejuar sh\u00ebrbimet e nevojshme dhe p\u00ebr t'u rifilluar firewalli:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo firewall-cmd --permanent --zone=public --add-service=http\nsudo firewall-cmd --permanent --zone=public --add-port=8181\/tcp\nsudo firewall-cmd --reload<\/code><\/pre>\n<p><\/p>\n<h2 id=\"nastroyka-balansirovschika-nagruzki\">Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs<\/h2>\n<p><\/p>\n<p>Konfigurimi i HAProxy \u00ebsht\u00eb nj\u00eb proces mjaft i thjesht\u00eb. N\u00eb thelb, gjith\u00e7ka q\u00eb duhet t\u00eb b\u00ebni \u00ebsht\u00eb t\u00eb informoni HAProxy se cilat lidhje duhet t\u00eb d\u00ebgjoj\u00eb dhe ku duhet t'i transmetoj\u00eb ato.<\/p>\n<p><\/p>\n<p>Kjo b\u00ebhet duke krijuar nj\u00eb skedar konfigurimi \/etc\/haproxy\/haproxy.cfg me cil\u00ebsimet p\u00ebrkat\u00ebse. Mund t\u00eb lexoni rreth parametrave t\u00eb konfigurimit t\u00eb HAProxy <noindex><a rel=\"nofollow\" href=\"https:\/\/cbonte.github.io\/haproxy-dconv\/2.0\/configuration.html\">n\u00eb faqen e dokumentacionit<\/a><\/noindex>, n\u00ebse d\u00ebshironi t\u00eb m\u00ebsoni m\u00eb shum\u00eb rreth k\u00ebsaj.<\/p>\n<p><\/p>\n<h2 id=\"balansirovka-nagruzki-na-transportnom-urovne-layer-4\">Balancimi i ngarkes\u00ebs n\u00eb nivelin e transportit (layer 4)<\/h2>\n<p><\/p>\n<p>Le t\u00eb fillojm\u00eb me konfigurimin bazik. Krijoni nj\u00eb skedar t\u00eb ri konfigurimi, p\u00ebr shembull, duke p\u00ebrdorur <strong>vi<\/strong> me komand\u00ebn m\u00eb posht\u00eb:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo vi \/etc\/haproxy\/haproxy.cfg<\/code><\/pre>\n<p><\/p>\n<p>Shtoni n\u00eb skedar seksionet e m\u00ebposhtme. Z\u00ebvend\u00ebsoni <strong>server_name<\/strong> me at\u00eb q\u00eb duhet t\u00eb th\u00ebrras\u00eb serverat tuaj n\u00eb faqen e statistikave, dhe <strong>private_ip<\/strong> me adresat IP private t\u00eb serverave, t\u00eb cilat d\u00ebshironi t\u00eb drejtoni trafikun web. Mund t\u00eb kontrolloni adresat IP private <noindex><a rel=\"nofollow\" href=\"https:\/\/hub.upcloud.com\/networks\/private?_ga=2.194047085.1141044831.1595511160-752947894.1595511160\">n\u00eb panelin e kontrollit UpCloud<\/a><\/noindex> dhe n\u00eb sked\u00ebn <em>Private network<\/em> n\u00eb menun\u00eb <em>Network\nglobal\n   log \/dev\/log local0\n   log \/dev\/log local1 notice\n   chroot \/var\/lib\/haproxy\n   stats timeout 30s\n   user haproxy\n   group haproxy\n   daemon\n\ndefaults\n   log global\n   mode http\n   option httplog\n   option dontlognull\n   timeout connect 5000\n   timeout client 50000\n   timeout server 50000\n\nfrontend http_front\n   bind *:80\n   stats uri \/haproxy?stats\n   default_backend http_back\n\nbackend http_back\n   balance roundrobin\n   server server_name1 private_ip1:80 check\n   server server_name2 private_ip2:80 check<\/em>.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">Kjo p\u00ebrcakton balancuesin e ngarkes\u00ebs n\u00eb nivelin e transportit (layer 4) me emrin e jasht\u00ebm http_front, duke d\u00ebgjuar n\u00eb portin 80, i cili pastaj drejton trafikun n\u00eb back-endin e paracaktuar me emrin http_back. Statistikat shtes\u00eb \/haproxy?stats lidhin faqen e statistikave n\u00eb adres\u00ebn e dh\u00ebn\u00eb.<\/code><\/pre>\n<p><\/p>\n<p>Algoritmet e ndryshme t\u00eb balancimit t\u00eb ngarkes\u00ebs.<\/p>\n<p><\/p>\n<h2 id=\"razlichnye-algoritmy-balansirovki-nagruzki\">P\u00ebrcaktimi i server\u00ebve n\u00eb seksionin e back-endit lejon HAProxy t\u00eb p\u00ebrdor\u00eb k\u00ebta server\u00eb p\u00ebr balancimin e ngarkes\u00ebs sipas algoritmit t\u00eb rrotullimit kur \u00ebsht\u00eb e mundur.<\/h2>\n<p><\/p>\n<p>Algoritmet e balancimit p\u00ebrdoren p\u00ebr t\u00eb p\u00ebrcaktuar se n\u00eb cilin server n\u00eb back-end d\u00ebrgohet \u00e7do lidhje. Ja disa nga opsionet e dobishme:<\/p>\n<p><\/p>\n<p>Roundrobin:<\/p>\n<p><\/p>\n<ul>\n<li><strong>\u00e7do server p\u00ebrdoret nj\u00ebher\u00eb pas tjetr\u00ebs sipas pesh\u00ebs s\u00eb tij. Ky \u00ebsht\u00eb algoritmi m\u00eb i qet\u00eb dhe m\u00eb i drejt\u00eb, kur koha e p\u00ebrpunimit nga server\u00ebt mbetet e shp\u00ebrndar\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb barabart\u00eb. Ky algorit\u00ebm \u00ebsht\u00eb dinamik, duke lejuar rregullimin e pesh\u00ebs s\u00eb serverit n\u00eb koh\u00eb reale.<\/strong> Leastconn:<\/li>\n<li><strong>M\u00eb pak lidhje:<\/strong> Zgjidhet serveri me numrin m\u00eb t\u00eb vog\u00ebl t\u00eb lidhjeve. Kjo b\u00ebhet p\u00ebrmes nj\u00eb cikli mes server\u00ebve me ngarkes\u00eb t\u00eb nj\u00ebjt\u00eb. P\u00ebrdorimi i k\u00ebtij algoritmi rekomandohet p\u00ebr seancat e gjata, si LDAP, SQL, TSE, etj., por nuk \u00ebsht\u00eb shum\u00eb i p\u00ebrshtatsh\u00ebm p\u00ebr seancat e shkurtra, si HTTP.<\/li>\n<li><strong>S\u00eb pari:<\/strong> serveri i par\u00eb me vende t\u00eb lira p\u00ebr lidhje merr lidhjen. Server\u00ebt zgjidhen nga identifikuesi m\u00eb i ul\u00ebt numerik deri te ai m\u00eb i larti, q\u00eb p\u00ebr default p\u00ebrkon me pozitat e server\u00ebve n\u00eb ferm\u00eb. Pasi serveri arrin vler\u00ebn maxconn, p\u00ebrdoret serveri tjet\u00ebr.<\/li>\n<li><strong>Burimi:<\/strong> Adresa IP e burimit hash-izohet dhe ndahet me pesh\u00ebn e p\u00ebrgjithshme t\u00eb server\u00ebve t\u00eb hapur, p\u00ebr t\u00eb p\u00ebrcaktuar se cili server do t\u00eb marr\u00eb k\u00ebrkes\u00ebn. K\u00ebshtu, e nj\u00ebjta adres\u00eb IP e klientit do t'i d\u00ebrgohet gjithmon\u00eb t\u00eb nj\u00ebjtit server, nd\u00ebrsa server\u00ebt mbeten t\u00eb pandryshuar.<\/li>\n<\/ul>\n<p><\/p>\n<h2 id=\"nastroyka-balansirovki-nagruzki-na-prikladnom-urovne-layer-7\">Konfigurimi i balancimit t\u00eb ngarkes\u00ebs n\u00eb nivelin e aplikacionit (layer 7)<\/h2>\n<p><\/p>\n<p>Nj\u00eb mund\u00ebsi tjet\u00ebr n\u00eb dispozicion \u00ebsht\u00eb t\u00eb konfiguroni balancuesin e ngarkes\u00ebs p\u00ebr t\u00eb punuar n\u00eb nivelin e aplikacionit (layer 7), e cila \u00ebsht\u00eb e dobishme kur pjes\u00eb t\u00eb aplikacionit tuaj web jan\u00eb t\u00eb vendosura n\u00eb hoste t\u00eb ndrysh\u00ebm. Kjo mund t\u00eb arrihet duke rregulluar kalimin e lidhjeve, p\u00ebr shembull, sipas URL-s\u00eb.<\/p>\n<p><\/p>\n<p>Hapni skedarin e konfigurat\u00ebs HAProxy me nj\u00eb editor teksti:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo vi \/etc\/haproxy\/haproxy.cfg<\/code><\/pre>\n<p><\/p>\n<p>M\u00eb pas konfiguroni segmentet frontend dhe backend sipas shembujve t\u00eb m\u00ebposht\u00ebm:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">frontend http_front\n   bind *:80\n   stats uri \\\/haproxy?stats\n   acl url_blog path_beg \\\/blog\n   use_backend blog_back if url_blog\n   default_backend http_back\n\nbackend http_back\n   balance roundrobin\n   server server_name1 private_ip1:80 check\n   server server_name2 private_ip2:80 check\n\nbackend blog_back\n   server server_name3 private_ip3:80 check<\/code><\/pre>\n<p><\/p>\n<p>Frontend deklaron nj\u00eb rregull ACL me emrin url_blog, i cili aplikohet p\u00ebr t\u00eb gjitha lidhjet me rrug\u00eb q\u00eb fillojn\u00eb me \\\/blog. Use_backend p\u00ebrcakton q\u00eb lidhjet q\u00eb p\u00ebrputhen me kushtin url_blog, duhet t\u00eb sh\u00ebrbehen nga backend me emrin blog_back, nd\u00ebrsa t\u00eb gjitha k\u00ebrkesat e tjera menaxhohen nga backend-i p\u00ebr default.<\/p>\n<p><\/p>\n<p>Nga an\u00ebtar\u00ebt e backend-it, konfigurimi vendos dy grupe server\u00ebsh: http_back, ashtu si m\u00eb par\u00eb, dhe nj\u00eb t\u00eb re, t\u00eb quajtur blog_back, e cila sh\u00ebrben lidhjet me example.com\\\/blog.<\/p>\n<p><\/p>\n<p>Pas ndryshimit t\u00eb konfigurimeve, ruani skedarin dhe rinisni HAProxy me komand\u00ebn e m\u00ebposhtme:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo systemctl restart haproxy<\/code><\/pre>\n<p><\/p>\n<p>N\u00ebse gjat\u00eb nisjes keni marr\u00eb ndonj\u00eb paralajm\u00ebrim ose mesazh gabimi, kontrolloni konfigurimin p\u00ebr ta dhe sigurohuni q\u00eb keni krijuar t\u00eb gjitha skedar\u00ebt dhe direktor\u00ebt e nevojsh\u00ebm, pastaj provoni p\u00ebrs\u00ebri t\u00eb rifilloni.<\/p>\n<p><\/p>\n<h2 id=\"testirovanie-nastroyki\">Testimi i konfigurimit<\/h2>\n<p><\/p>\n<p>Kur HAProxy \u00ebsht\u00eb konfiguruar dhe e nisi, hapni IP-n\u00eb publike t\u00eb serverit t\u00eb balancuesit t\u00eb ngarkes\u00ebs n\u00eb shfletues dhe kontrolloni n\u00ebse jeni lidhur sakt\u00eb me backendin. Parametri stats uri n\u00eb konfigurim krijon nj\u00eb faqe statistikash n\u00eb adres\u00ebn e specifikuar.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">http:\/\/load_balancer_public_ip\/haproxy?stats<\/code><\/pre>\n<p><\/p>\n<p>Kur t\u00eb ngarkoni faqen e statistikave, n\u00ebse t\u00eb gjith\u00eb serverat tuaj shfaqen me ngjyr\u00eb t\u00eb gjelb\u00ebr, at\u00ebher\u00eb konfigurimi \u00ebsht\u00eb realizuar me sukses!<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Instalimi i balancuesit t\u00eb ngarkes\u00ebs HAProxy n\u00eb CentOS\" src=\"\/wp-content\/uploads\/2020\/07\/ce912c5824d0294537b984fe04bdcc8b.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Faqja e statistikave p\u00ebrmban informacion t\u00eb dobish\u00ebm p\u00ebr ndjekjen e hosteve tuaj t\u00eb uebit, duke p\u00ebrfshir\u00eb koh\u00ebn e pun\u00ebs\/ndalimit dhe numrin e seancave. N\u00ebse ndonj\u00eb server \u00ebsht\u00eb marr\u00eb me ngjyr\u00eb t\u00eb kuqe, sigurohuni q\u00eb serveri \u00ebsht\u00eb i ndezur dhe se mund ta pingoni nga makina e balancuesit t\u00eb ngarkes\u00ebs.<\/p>\n<p><\/p>\n<p>N\u00ebse balancuesi juaj i ngarkes\u00ebs nuk po p\u00ebrgjigjet, sigurohuni q\u00eb lidhjet HTTP nuk jan\u00eb bllokuar nga firewall-i. Po ashtu, sigurohuni q\u00eb HAProxy \u00ebsht\u00eb duke funksionuar duke p\u00ebrdorur komand\u00ebn m\u00eb posht\u00eb:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo systemctl status haproxy<\/code><\/pre>\n<p><\/p>\n<h2 id=\"zaschita-stranicy-statistiki-s-pomoschyu-parolya\">Mbrojtja e faqes s\u00eb statistikave me fjal\u00ebkalim<\/h2>\n<p><\/p>\n<p>Megjithat\u00eb, n\u00ebse faqja e statistikave \u00ebsht\u00eb e ndaluar vet\u00ebm n\u00eb frontend, at\u00ebher\u00eb ajo \u00ebsht\u00eb e hapur p\u00ebr shikimin publik, q\u00eb mund t\u00eb jet\u00eb nj\u00eb ide e keqe. N\u00eb vend t\u00eb k\u00ebsaj, mund t'i caktoni nj\u00eb num\u00ebr porti t\u00eb ve\u00e7ant\u00eb, duke shtuar shembullin m\u00eb posht\u00eb n\u00eb fund t\u00eb skedarit tuaj haproxy.cfg. Z\u00ebvend\u00ebsoni <strong>username<\/strong> dhe <strong>password<\/strong> me di\u00e7ka t\u00eb sigurt:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">listen stats\n   bind *:8181\n   stats enable\n   stats uri \/\n   stats realm Haproxy Statistics\n   stats auth username:password<\/code><\/pre>\n<p><\/p>\n<p>Pas shtimit t\u00eb grupit t\u00eb ri t\u00eb d\u00ebgjuesve, hiqni lidhjen e vjet\u00ebr p\u00ebr stats uri nga grupi i frontendit. Kur t\u00eb p\u00ebrfundoni, ruani skedarin dhe rifilloni HAProxy.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">sudo systemctl restart haproxy<\/code><\/pre>\n<p><\/p>\n<p>Pastaj hapni p\u00ebrs\u00ebri balancuesin e ngarkes\u00ebs me numrin e ri t\u00eb portit dhe hyni me emrin e p\u00ebrdoruesit dhe fjal\u00ebkalimin q\u00eb keni caktuar n\u00eb skedarin e konfigurimit.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">http:\/\/load_balancer_public_ip:8181<\/code><\/pre>\n<p><\/p>\n<p>Sigurohuni q\u00eb t\u00eb gjith\u00eb serverat tuaj t\u00eb vijojn\u00eb t\u00eb shfaqen me ngjyr\u00eb t\u00eb gjelb\u00ebr dhe pastaj hapni vet\u00ebm IP-n\u00eb e balancuesit t\u00eb ngarkes\u00ebs pa ndonj\u00eb num\u00ebr porti n\u00eb shfletuesin tuaj.<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">http:\/\/load_balancer_public_ip\/<\/code><\/pre>\n<p><\/p>\n<p>N\u00ebse keni ndonj\u00eb larmi faqesh q\u00ebllimi n\u00eb serverat tuaj t\u00eb brendsh\u00ebm, do t\u00eb v\u00ebreni se \u00e7do her\u00eb q\u00eb rifreskoni faqen, merrni nj\u00eb p\u00ebrgjigje nga nj\u00eb host tjet\u00ebr. Mund t\u00eb provoni algoriteme t\u00eb ndryshme t\u00eb balancimit n\u00eb seksionin e konfigurimit ose t\u00eb njiheni me <noindex><a rel=\"nofollow\" href=\"https:\/\/cbonte.github.io\/haproxy-dconv\/\">dokumentacionin e plot\u00eb<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h2 id=\"zaklyuchenie-balansirovschik-nagruzki-haproxy\">P\u00ebrfundim: balancuesi i ngarkes\u00ebs HAProxy<\/h2>\n<p><\/p>\n<p>Grat\u00ebsoni p\u00ebr konfigurimin e suksessh\u00ebm t\u00eb balancuesit t\u00eb ngarkes\u00ebs HAProxy! Edhe me nj\u00eb konfigurim bazik t\u00eb balancimit t\u00eb ngarkes\u00ebs, mund t\u00eb p\u00ebrmir\u00ebsoni ndjesh\u00ebm performanc\u00ebn dhe disponueshm\u00ebrin\u00eb e aplikacionit tuaj web. Ky udh\u00ebzues \u00ebsht\u00eb vet\u00ebm nj\u00eb hyrje n\u00eb balancimin e ngarkes\u00ebs me HAProxy, i cili \u00ebsht\u00eb n\u00eb gjendje t\u00eb b\u00ebj\u00eb shum\u00eb m\u00eb tep\u00ebr sesa mund t\u00eb p\u00ebrshkruhet n\u00eb nj\u00eb udh\u00ebzues t\u00eb shkurt\u00ebr konfigurimi. Ne rekomandojm\u00eb t\u00eb eksperimentoni me konfigurime t\u00eb ndryshme duke p\u00ebrdorur <noindex><a rel=\"nofollow\" href=\"https:\/\/cbonte.github.io\/haproxy-dconv\/2.0\/configuration.html\">dokumenationin e gjer\u00eb<\/a><\/noindex>, t\u00eb disponuesh\u00ebm p\u00ebr HAProxy, dhe pastaj t\u00eb filloni planifikimin e balancimit t\u00eb ngarkes\u00ebs p\u00ebr ambientin tuaj prodhues.<\/p>\n<p><\/p>\n<p>Duke p\u00ebrdorur disa hoste p\u00ebr t\u00eb mbrojtur sh\u00ebrbimin tuaj web me nj\u00eb rezerv\u00eb fuqie, balancuesi i ngarkes\u00ebs vet\u00eb mund t\u00eb p\u00ebrfaq\u00ebsoj\u00eb nj\u00eb pik\u00eb d\u00ebshtimi. Mund t\u00eb rrisni m\u00eb tej disponueshm\u00ebrin\u00eb e lart\u00eb duke vendosur nj\u00eb IP t\u00eb l\u00ebvizshme midis disa balancuesve t\u00eb ngarkes\u00ebs. Mund t\u00eb m\u00ebsoni m\u00eb shum\u00eb rreth k\u00ebsaj n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/upcloud.com\/community\/tutorials\/floating-ip-addresses\/\">artikullin ton\u00eb mbi adresat IP t\u00eb l\u00ebvizshme n\u00eb UpCloud<\/a><\/noindex>.<\/p>\n<p>M\u00eb shum\u00eb rreth kursit <noindex><a rel=\"nofollow\" href=\"https:\/\/otus.pw\/KbNT\/\">\u00abAdministratori Linux. Virtualizimi dhe klasterizimi\u00bb<\/a><\/noindex>***<\/p>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/otus\/blog\/512238\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043b\u0435\u043d \u0432 \u043f\u0440\u0435\u0434\u0434\u0432\u0435\u0440\u0438\u0438 \u0441\u0442\u0430\u0440\u0442\u0430 \u043a\u0443\u0440\u0441\u0430 \u00ab\u0410\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440 Linux. \u0412\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u0438 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0438\u0437\u0430\u0446\u0438\u044f\u00bb \u0411\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u2014 \u044d\u0442\u043e \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u043d\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 \u0434\u043b\u044f \u0433\u043e\u0440\u0438\u0437\u043e\u043d\u0442\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0432\u0435\u0431-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439 \u043f\u043e \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u0438\u043c \u0445\u043e\u0441\u0442\u0430\u043c \u0441 \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u0435\u043c \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c \u0435\u0434\u0438\u043d\u043e\u0439 \u0442\u043e\u0447\u043a\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u0441\u0435\u0440\u0432\u0438\u0441\u0443. HAProxy \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u0441\u0430\u043c\u044b\u0445 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u044b\u0445 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c \u0434\u043b\u044f \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0438 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0441 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u043c \u0438\u0441\u0445\u043e\u0434\u043d\u044b\u043c \u043a\u043e\u0434\u043e\u043c, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0442\u0430\u043a\u0436\u0435 \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0438\u0432\u0430\u0435\u0442 \u0432\u044b\u0441\u043e\u043a\u0443\u044e \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u043e\u0441\u0442\u044c \u0438 \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u043f\u0440\u043e\u043a\u0441\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f. [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":89713,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-89711","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043b\u0435\u043d \u0432 \u043f\u0440\u0435\u0434\u0434\u0432\u0435\u0440\u0438\u0438 \u0441\u0442\u0430\u0440\u0442\u0430 \u043a\u0443\u0440\u0441\u0430 \u00ab\u0410\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440 Linux.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ustanavlivaem-balansirovshhik-nagruzki-haproxy-na-centos\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0423\u0441\u0442\u0430\u043d\u0430\u0432\u043b\u0438\u0432\u0430\u0435\u043c \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 HAProxy \u043d\u0430 CentOS | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043b\u0435\u043d \u0432 \u043f\u0440\u0435\u0434\u0434\u0432\u0435\u0440\u0438\u0438 \u0441\u0442\u0430\u0440\u0442\u0430 \u043a\u0443\u0440\u0441\u0430 \u00ab\u0410\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440 Linux.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ustanavlivaem-balansirovshhik-nagruzki-haproxy-na-centos\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-07-25T11:42:31+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-07-25T11:42:31+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Instalimi i balancuesit t\u00eb ngarkes\u00ebs HAProxy n\u00eb CentOS | ProHoster","description":"P\u00ebrkthimi i artikullit \u00ebsht\u00eb p\u00ebrgatitur n\u00eb prag t\u00eb fillimit t\u00eb kursit \"Administrator Linux.\"","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ustanavlivaem-balansirovshhik-nagruzki-haproxy-na-centos","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0423\u0441\u0442\u0430\u043d\u0430\u0432\u043b\u0438\u0432\u0430\u0435\u043c \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 HAProxy \u043d\u0430 CentOS | ProHoster","og:description":"\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441\u0442\u0430\u0442\u044c\u0438 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043b\u0435\u043d \u0432 \u043f\u0440\u0435\u0434\u0434\u0432\u0435\u0440\u0438\u0438 \u0441\u0442\u0430\u0440\u0442\u0430 \u043a\u0443\u0440\u0441\u0430 \u00ab\u0410\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440 Linux.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ustanavlivaem-balansirovshhik-nagruzki-haproxy-na-centos","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-07-25T11:42:31+00:00","article:modified_time":"2020-07-25T11:42:31+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"89711","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 13:05:27","updated":"2022-10-04 12:00:44","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/89711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=89711"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/89711\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/89713"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=89711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=89711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=89711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}