Files
wireguard_webadmin/locale/sk/LC_MESSAGES/django.mo
T

573 lines
122 KiB
Modelica
Raw Normal View History

2026-11-20 21:58:17 -03:00
ή•΅$α,:°M½±MΆoPSTmfVΤYήνZ~Μ\‚K]wΞ]F^3d_ƒ�`xf•f�§hωBiρ<j.m�JpΦυu\Μw�){lΈ}&%‚L…Ii†­³�~a�Oΰ•30–Fd–:«—]ζ—/D�+t�' �Θ�Ο�α���™ $™
.™<™L™#\™!€™Ά™©™±™Έ™ Ό™Θ™Ϊ™ν™�™�$�:�J�[�n�~� —�΅��� Ή�Ζ� Υ� α�λ�›››
2›=›
E›S›‰W›α› η›
�6� I�
V�0d�?•�%Υ�ϋ�$�">�#a�!…�§�ΐ�Ο� ε�ρ� �'$�QL� �� ��0�.η��&*�$Q�v�'��%°�Φ�!ι�   + ¥8 ‘ή p΅v΅‹΅+�΅7Ζ΅>ώ΅==Ά={Ά@ΉΆ>ϊΆ;9£Eu£5»£8ρ£7*¤@b¤8£¤3ά¤[¥Bl¥――¥@_¦R ¦ σ¦ �¦ §§+1§)]§‡§�§ ²§6Σ§6
¨A¨1_¨‘¨®¨ ³¨ΐ¨�¨ζ¨©©q ©l’©v�©Xv�SΟ�A#«He«7®« ζ«ς«)¬0¬4@¬u¬z¬€¬�¬�¬»¬
Α¬Ο¬Χ¬υ¬ ­­#­;:­&v­�­­­�΄­$Q®v®…®–®�®®®;³® ο―ω―°°)°F°[°s°�° �°¦°Β°Ϊ°Nϊ°I± b±o±
†±A”±Φ±θ±$χ±"²?²O²$g²%�²6²²$ι²4³2C³>v³2µ³0θ³"΄$<΄a΄r΄�΄4”΄)Ι΄σ΄!
µ/µ4µ;µMµUµ,dµ‘µ¨µΉµΘµβµ4σµC(JlF·¶ώ¶··)·?·T·!g·‰·΅·Ί·Χ·ν·ΈΈ .Έ:ΈRΈgΈ�Έ†Έ�—Έ Ή %Ή"1ΉTΉcΉ!tΉ–Ή§ΉΈΉ ΐΉΜΉΣΉάΉλΉΊΊ 2Ί?ΊWΊ^Ί²oΊ"»'»6»I»]»p»�»΅»·»Ξ»ι»ύ»Ό(Ό
8ΌFΌ UΌ _ΌiΌ{Ό�ΌΆΌΈΌ ΛΌ ΥΌ
αΌοΌ
υΌ
½½(½+7½
c½q½:‡½Β½
Κ½Ψ½
μ½χ½�½ ΎΎ'Ύ7Ύ:OΎ�Ύ›ΎOΊΎ<
ΏGΏMΏcΏDzΏ>ΏΏWώΏQVΐ_¨ΐKΑTΑnΑ‡Α—Α΄ΑOΠΑ Β5ΒDΒ;SΒ �ΒY›ΒυΒύΒ
ΓΓ0&Γ
WΓbΓ5wΓ
­ΓWΈΓΔ=�ΔΞΔγΔ%Ε)ΕGΕVΕiΕ"{Ε �Ε$ΏΕδΕ(Ζ+*Ζ)VΖ€Ζ‡Ζ �Ζ&›Ζ$ΒΖ%ηΖ#
Η1Η,BΗoΗwΗ�Η�Η
°Η»Η&ΒΗ ιΘυΘϊΘ%Ι)Ι/Ι
7ΙBΙARΙ ”Ι/µΙεΙ ΚΚΚ/)Κ3YΚ3�Κ4ΑΚWφΚNΛcWΛ»Λ ΎΛΛΛ ΤΛαΛ κΛφΛ ΜΜ Μ4ΜEΜ@MΜ�Μ: ΜΫΜλΜϋΜFΝVΝuΝO‡Ν!ΧΝωΝΞ,Ξ
EΞ$PΞ&uΞ�ΞΊΞ ΜΞνΞςΞ ϋΞ ΟΟ %Ο1Ο=BΟG€ΟΘΟΠΟ#ΰΟΠΠ*Π
3Π >ΠJΠYΠbΠ hΠ
tΠΠ�Π–Π«ΠΔΠαΠώΠΡ&Ρ"8Ρ[ΡxΡ €Ρ�Ρ_�Ρ�Ρ�#�(�7�?�E�I� `� m� y� †�’�•�#―�Σ� κ� Σ%ΣAΣ)\Σ†Σ–Σ*­ΣΨΣυΣ Τ*Τ1DΤBvΤ$ΉΤ ήΤ�Τ"Υ8Υ2PΥƒΥ�Υ-ΈΥζΥόΥ
Φ Φ
!Φ/Φ7ΦFΦYΦJkΦ<¶Φ2σΦ&Χ$.ΧSΧlΧ@sΧ΄ΧΜΧJβΧ-Ψ3Ψ
7Ψ EΨ
RΨ]ΨfΨ0|Ψ<­Ψ#κΨΩ,$Ω4QΩ*†Ω4±ΩζΩ ώΩ"
Ϊ(-ΪVΪuΪzΪ�Ϊ'ΆΪ,ΚΪ χΪΫ "Ϋ5,Ϋ bΫ
oΫ
}Ϋ �Ϋ8•Ϋ'ΞΫ'φΫ,άKά<jά-§άΥά:ςά4-έ'bέ�έ�έH�έαέπέ ήήI*ή9tή#®ή/�ή1ί"4ί2Wί4�ί1Ώί$ρίΰ ΰ)ΰ8.ΰ3gΰ ›ΰ¨ΰ&Ίΰ$αΰαα
'α?5α uα�α�α©α»α+Δα πα όα βββ%β,β
;βhFβ―β·βΎβΕβΥβπβ5γ
=γHγWγfγnγ;γ»γΓγ�γγγόγ9δUδ^δrδ΅�δ.ε@εPεbε|ε�ε
–ε
΅ε¬ε$Βε%ηε
ζζ#*ζNζ3_ζ2“ζΖζ
Ψζ ζζ&ςζη"η'η&0η$Wη|η�η¥ηΔηDΦηθF/θ vθ
€θh�θχθ�θι2 ι.Sι7‚ιLΊι κκ+κHκdκkκ&{κΆκ«κ"Ύκακ
λ λλ
2λ =λ6Iλ
€λ‹λ ’λ �λ¨λ Ελ
ΟλΪλ
ΰλλλ+ μ7μUμfμƒμ�μ‘μ™μ ³μ ΏμjΙμ4ν DνQν Vνbν0vνA§ν<ιν2&ξDYξ:�ξ
Ωξηξφξ ϋξο=ο¬\ο„ π‚�πDρ5Vρ6�ρ»Γρ&ςt¦σhτN„τ–ΣτzjυευGeφ)­φ9ΧφIχ:[χ9–χ?Πχ%ψ?6ψ$vψK›ψ?ηψ;'ωecω5ΙωG�ωEGϊ*�ϊ:Έϊ®σϊ"Άϋ#Εϋ_ιϋxIό'Βόκό)ύ4,ύxaύ5Ϊύ+ώ<ώFB�(‰�
²�½�#Ζ�!κ� !t=²ΓΙ
ιχ$%-S[`<d9΅ Ϋημ
τ  0EUo‰¤¬#µ0Ωi
ItΙΎ%�
® ΉΖβ@ώ&?f‚‹‘
 «Ύ�ζο χ 
¦ΓΩ ξψ#=Pdv�›°Γ)Χ;=={�‘ ΐΰ(φX x “ ³ » Κ &Ξ …υ {


‡
•

¦
 ΄
ΐ
2025-08-12 08:54:05 -03:00
 �
Rσ
F ed Κ �κ ϋx
�tvxx&ρ�…§�…FKΜQ £j!“'SΆ'£φ)$�*hΏ+¬(/ΘΥ2�9®Ί;Θi?¬2BoίFUOJγ¥KΣ‰Rθ]VQF\9�\t�\:G^_‚^6β^+_%E_k_s_$…_$�_ Ο_ ά_ζ_ϋ_`/!`,Q`~`„`�`“`›`―`Κ`δ`ύ`a.aGaga€a–a)¬aΦaζaωa bb1b
@bNbkb…b�bΉbΘbΟbήb‰ζbpcyc‰c! cΒcΰcφcd)(dERd.�d"Ηd.κd+e,Ee)re�eΈeΚeγeχe$ f+1fU]f ³f
Ώf<Κf9gAg0Zg-‹gΉg-Οg*ύg(h'9h$ah
†h―‘hΆAi
δiοi
j. j<Oj3�j2ΐjCσj97k7qk;©k=εk-#l4Ql7†l6Ύl8υl2.mLamI®mΉψm@²nhσn\oto�o�o4΄o1ιop3p-GpCupDΉp,ώpC+q*oq�q΅q
²qΐqCΠqr+r{4r~°r•/sZΕs\ tI}tNΗt=u Tu`u>zu
Ήu;Ηuv vv!v"4vWv`vqv.yv¨vΊvΙvάvIυv,?wlw
|w­�w*8xcxzx�x’x ¤x:°xλyόyz!z!6zXztz#‘zµzΚz'Ωz{${SC{—{µ{Δ{έ{Jμ{7|
I|*W|'‚|
�|Έ|)Χ|*}?,})l}>–}8Υ}B~HQ~;�~)Φ~./ BN>i5¨ ή)�)€ 2€<€M€b€6{€"²€Υ€η€ό€�-0�L^�U«�L‚N‚W‚l‚‹‚©‚Ζ‚+έ‚! ƒ+ƒ#Hƒlƒ†ƒ%¥ƒΛƒ
αƒοƒ„)„
G„R„—o„…
…)… =…J… Y…z…
‰… ”…  … ¬…
¶…Α…$�…χ…†)† =†^†f†Π†P‡Y‡p‡�‡§‡Α‡(Υ‡ώ‡� 7�X�o�"‹�®�Α�Υ�θ�ϊ� ‰!‰7‰W‰s‰�‰¦‰¶‰Θ‰Ο‰ΰ‰π‰
�7 �X�h�;�� Δ�Ξ�ή� φ�‹‹
"‹0‹N‹b‹A€‹Β‹%Χ‹^ύ‹K\�¨� ®� Ο�Tπ�BE�e��dξ�}S�_Ρ�1� Q� r�3“�'Η�Nο�>�]�t�L‹� Ψ�yδ�^‘ g‘
q‘|‘/‘‘ Α‘Λ‘9ε‘’Y1’~‹’M
“ X“+y“:¥“/ΰ“”"”<”*P”*{”,¦”.Σ”:•==•&{•Ά•�•±•/Ι•,ω•4&–1[–�–2§– Ϊ–ζ–ύ–—0—?—VG—�� ­�·�+Ι� υ� ™ ™™C&™&j™3‘™#Ε™ ι™ σ™ύ™5�7G�A�=Α�K��K›]T›²›Έ›
Λ› Φ›
γ›
ξ›ό› ��1�D� S�>]���H°�ω�
��I<�+†�²�XΟ�,(�U�e�9z�
΄�+Β�-ξ�#�@�._���—���―�Η�β�ϊ�S Nb  ± » 'Π ψ ΅ %΅1΅H΅
2026-01-27 15:22:12 -03:00
Y΅ g΅s΅‚΅
—΅Ά΅
΄΅Ώ΅ά΅ ϋ΅#Ά@Ά`Ά|Ά#�Ά-°Ά ήΆθΆϊΆY £e£ƒ£�£“£©£Ή£Ώ£Ε£ΰ£ψ£¤'¤>¤'B¤2j¤�¤,½¤"κ¤'
¥.5¥?d¥¤¥Δ¥:γ¥(¦G¦)d¦�¦?­¦Wν¦&E§2l§ �§+ΐ§*μ§F¨(^¨'‡¨:―¨(κ¨
©
!© /©9© K©X©h©|©K”©Cΰ©8$�]�&e���¦�M­�ϋ�«T-«‚«�«’« §« ³«½«Γ«9Τ«G¬.V¬…¬!�¬3Ί¬,ξ¬5­Q­ g­+t­( ­)Ι­σ­ψ­ ®/!®3Q® …®’®
©®=·®
υ® ―
――2,―._―,�―2»―ξ―Y °6f°�°YΊ°8±6M±„±�±J‘±ά±5ν± #²/²FA²<�²*Ε²8π²')³"Q³Dt³AΉ³>ϋ³8:΄s΄ |΄‰΄7�΄7Ζ΄ώ΄µ6/µ6fµ�µ―µΙµ@Ωµ
(FWk,t΅¶΄¶
Γ¶Ξ¶
Χ¶ε¶ξ¶ώ¶Z·j·
r·}·…·•·³·5Ν· ΈΈ#Έ 6ΈBΈ?UΈ
•Έ Έ»Έ"ΦΈ"ωΈDΉaΉ$jΉ+�Ήΐ»Ή|Ί‹Ί�Ί¶ΊΦΊσΊ ϊΊ »».0»=_»�»£»%Ύ»δ»?ω»;9ΌuΌ�Ό�Ό%­ΌΣΌΪΌ γΌ+πΌ+½H½\½v½‘½H¬½$υ½HΎ
cΎnΎ~~ΎύΎΏ! Ώ4.Ώ<cΏ= ΏdήΏCΐSΐ+oΐ!›ΐ½ΐΔΐ,ΧΐΑ Α$ Α)EΑoΑ
‚Α(�Α¶ΑΗΑ=ΩΑΒ)Β /Β<Β KΒlΒ{Β�Β
�Β%�Β2ΓΒ%φΒΓ1;ΓmΓrΓ zÆæà ΈΓ€ΕΓFΔVΔgΔlΔ{Δ4�Δ@ΕΔGΕ<NΕM‹ΕBΩΕΖ-Ζ=ΖBΖSΖMnΖΆΌΖ„_ΗuδΗ;ZΘ9–Θ6ΠΘΡΙ4ΩΙmΛ`|ΛLέΛ�*Μ~ΚΜ�IΝI�Ν3Ξ6PΞK‡Ξ6ΣΞ<
ΟFGΟ�ΟF¤Ο λΟV ΠIcΠ;­ΠzιΠ4dΡR™ΡUμΡ1B�>t�³�+jΣ(–ΣiΏΣ‰)Τ#³ΤΧΤ6ξΤ0%ΥƒVΥ8ΪΥ-ΦAΦOSΧ'£Χ
ΛΧΩΧ*βΧ*
Ψ8Ψ/KΨ{{ΨχΨΩ"Ω8ΩHΩ
OΩ,]Ω-�ΩΈΩΏΩΓΩHΗΩ>Ϊ OΪ[ΪdΪmΪ|Ϊ�Ϊ �Ϊ¬ΪΔΪΰΪ"ψΪ(Ϋ%DΫ
jΫxΫ0�Ϋ0²ΫƒγΫXgάΎΐά1έ±έΙέ3αέ1ήPGή3�ή;Μήίί.ί
EίSίmί†ί�ί ί§ίΉί
ΛίΘΩίΆΰΊΰ�ΰΩΰβΰυΰα!α6αKα^αvα…α�α²α*ΗαEςα?8βxβ‡β�β%΅β#Ηβλβ,γ[0γ#�γ-°γήγζγυγϊγ�δ¨δ °δΊδΜδηδεε+0εV\ε%³εdΩε#>ζe_Ι+|υνM�…¬ίYΚ••T  α·=‡qΦ
!1BrC‹{ώΘ·¨φbδ©xΗN)π��
‡ cτ
��W�AvϋΕ7o
2025-08-12 08:54:05 -03:00
ΑsΟΘ2� κd�Λ5&ΡΦ8o‘�­nί„€Β±|γ�=ζp°ΠVbΫ‰ΈθeχqΚ‘v9ύ‚a%TΓµj!�9‰φnζ�(ϋ1ΠM�XPη­Δt�FTQ»�’ξϋ£η@&yfό}\χ#:ΞU/άΙ0#„I™ΙHK€�ά,,q°θ‘@w®?c΄5>¨ ³MδIΨ�-†Ϋ_O­9�^ψβ¬�!S
u�ΎhjΎ�©Fψ†~οl¤h.©�
3-Δ–k±lΰε}ΏςFη 9)Κw*�]ξcΡλ[¥y$JLι��P�\ώ¬S5�›ϊΐ6�;" )pW ,lx�Χ&C 2ψ�Ήi�΄v’/Ν%Ω�~�zD.υL�'�ΐdόrmΖoμ^„bAL~�Q“ΥΘ�΅‰ςh@ΊΠ»€NS‚—ω½§|λ6�R^u.Zγ�">†“£θτ/χ‡nωkϊΥ�w*•G#(g¤° –β�ι]�ΨΓzV–β;{$;ΞE\Ζ<†ς1—RDZ]λΕ_»•sΥΧSjενέGG(Ώ m?γ0ώΝ”›ƒtΦH)§`υ+i‡Ν�w½Y@I«a‰�²'cO4‚―:
zπ}K‹―ƒP5ο{ϊΓ<hE�ECH΅FάU�ε EƒX’ύoτu1mΰ4έ�
ΌOΔ‹“Σο”�_νζΫ…4Ρ+ΌΆ<DΒδΟΩz®�½–�P"'µyr¥Ά�*v-J>΅VΉQXZB(ΈΤ‹¦<7Vd3‘Τ 0�3[ΉK+¦¤Ax#αή³a:µΪΩΧ�ΞyΈ£N/Rf`²π'Ηm-7―®rΐuΣ$ΟΖY� ΄|!e™ω2�pWiήΤέΪί±p kΜ^;A²g……ιG’‚Y—�%Λμ¥σ8™Ηd~LgU\g΅e3„Μό}t0fΣ�Ύ Α�CHZaO³”φ8”Xfb�JIρ4�JΏRΰή.lΜ›{ρ€Ε$q%s2&?«Ό>=« ρx6 `α›ΑƒΊNσUΊ: T�“*7�κk—κQ"μ6,[¦¨W�DξsintBΪ=·`ΛMj�[Ψ?B] �Ά™8§σύKΒ
<h5>Advanced VPN Firewall Configuration</h5>
<p>
This interface serves as a comprehensive tool for managing firewall rules, enabling users to implement advanced traffic policies between VPN peers and networks. It simplifies establishing firewall rules, packet filtering, and NAT configurations, allowing for precise control over network security. Users can define source and destination IP addresses, ports, protocols, and actions to tailor traffic flow, ensuring a secure and efficient networking environment.
</p>
<h5>Destination Selection</h5>
2026-03-13 20:44:45 -03:00
<p>
You have the option to apply this rule to a specific IP address or network and/or to multiple peers as the destination.<br><br>
Enabling the "Include peer networks" option will automatically include all Allowed IPs associated with each selected peer as the destination.<br><br>
Please note that selecting multiple peers with included networks on both the source and destination ends may result in a rapid increase in the number of firewall rules generated, depending on your configuration.<br><br>
The "Not Destination" option negates the selected destination IP, network, or peer(s).
</p>
<h5>Protocol and Port</h5>
<p>
Only the most commonly used protocols are listed here. If you require a specific protocol, please open an issue on GitHub.<br><br>
Selecting TCP+UDP will result in the duplication of generated rules.<br><br>
Ports can be specified as single numbers (e.g., 8080) or as ranges (e.g., 8001:8999).
</p>
2026-11-17 16:03:37 -03:00
<h5>Source Selection</h5>
<p>
You have the option to apply this rule to a specific IP address or network and/or to multiple peers.<br><br>
Enabling the "Include peer networks" option will automatically include all Allowed IPs associated with each selected peer.<br><br>
2026-03-18 11:24:10 -03:00
Please note that selecting multiple peers with included networks on both the source and destination ends may result in a rapid increase in the number of firewall rules generated, depending on your configuration.<br><br>
The "Not Source" option negates the selected source IP, network, or peer(s).
</p>
DNS servers pushed to peers.
<br>
Using the internal IP as primary DNS enables internal name resolution
and DNS filtering.
Enforces routing rules defined by routing templates using firewall rules.
<br>
Peers with a default route (0.0.0.0/0) are not restricted.
2026-03-15 17:31:19 -03:00
<br><br>
Note: depending on the number of routes and peers, this option may generate
a large number of firewall rules.
Internal IP address and netmask used by the WireGuard interface.
Interval used to refresh WireGuard status information in the web UI.
Optional name used only for display in the web interface.
Public hostname or IP address and UDP port used by peers to connect.
<br>
The <b>listen port</b> must be exposed and mapped in your Docker compose (YAML) file.
2025-08-12 08:54:05 -03:00
WireGuard private and public keys for this interface.
<br>
The private key must remain secret.
Changing it requires updating all peer configurations.
<h5>Default Ports</h5>
<p>The default <code>docker-compose.yml</code> file specifies the <b>TCP</b> port range <b>8080-8089</b>. If you wish to change the port forwarding to a different range, you must manually edit the <code>docker-compose.yml</code> file and rerun the Docker Compose step outlined in the <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">deployment instructions</a>.</p>
<h5>Destination Type: Peer</h5>
<p>Port redirection will prioritize the first Peer IP address assigned a priority of Zero.</p>
<h5>Destination Type: IP Address</h5>
<p>Port forwarding rules will redirect to the specified IP address. Remember to allocate the IP address or network to a Peer.</p>
<h5>Adding a Forward Rule</h5>
<p>Automatically generates a forwarding rule to accommodate stricter firewall settings.</p>
<h5>Masquerade Source</h5>
<p>This serves as a temporary solution when a peer does not use the VPN as its default gateway. It's important to note that this configuration is not recommended, as it alters the source address of all connections to match the IP address of the WireGuard instance.</p>
<h5>Deny Policy</h5>
<p>A Deny policy blocks all access to the matched routes.</p>
<h5>Protected Policy</h5>
<p>A Protected policy requires users to authenticate before accessing the application.</p>
<ul>
<li><strong>Allowed Groups</strong>: Limits access to specific user groups. Note: Using groups requires selecting an Authentication Method of type "Local Password".</li>
<li><strong>Authentication Methods</strong>: Specify which methods users can use to authenticate (e.g., Local Password, TOTP, OIDC).</li>
</ul>
2026-02-09 22:07:48 -03:00
<h5>Public Policy</h5>
<p>A Public policy allows access to the application without requiring any authentication.</p>
<div class="alert alert-warning">
This hostname is used to access WireGuard WebAdmin. If the certificate cannot be issued,
2025-12-29 18:30:39 -03:00
your browser will show a security warning until the problem is fixed.
2026-03-12 18:54:37 -03:00
</div>
<h4>Authentication Types</h4>
<p>Select how users will authenticate through this method.</p>
<h5>Local Password</h5>
<p>Users will authenticate using a standard username and password stored locally. Only one of this type can be created.</p>
<h5>OIDC (OpenID Connect)</h5>
2026-03-13 20:44:45 -03:00
<p>Users will authenticate via an external identity provider (like Keycloak or Google). Requires Provider URL, Client ID, and Client Secret.</p>
<h5>TOTP (Time-Based One-Time Password)</h5>
<p>Users will need to enter a rotating token from an authenticator app. If a user does not have a personal TOTP configured, the <strong>Global TOTP Secret</strong> will be used instead. </p>
<h4>Gatekeeper User</h4>
<p>Gatekeeper users are used for authenticating against protected applications managed by this gateway.</p>
2026-11-20 21:58:17 -03:00
<h5>Password</h5>
<p>Required when creating a user. When editing, leave both password fields blank to keep the current password.
Passwords are stored using <strong>Argon2id</strong> hashing.</p>
<h5>TOTP Secret</h5>
<p>Optional per-user TOTP secret. When set, this user will authenticate using their own secret instead of the
global TOTP secret configured on the Authentication Method. Use the buttons below the field to generate a
random secret and scan the QR code with your authenticator app. Validate the secret by entering the current
6-digit PIN before saving.</p>
<h4>User Levels</h4>
<h5>Debugging Analyst</h5>
<p>Access to basic system information and logs for troubleshooting. No access to modify settings or view sensitive data such as peer keys.</p>
2026-03-12 18:54:37 -03:00
<h5>View Only</h5>
<p>Full view access, including peer keys and configuration files. Cannot modify any settings or configurations.</p>
<h5>Peer Manager</h5>
<p>Permissions to add, edit, and remove peers and IP addresses. Does not include access to modify WireGuard instance configurations or higher-level settings.</p>
<h5>Wireguard Manager</h5>
<p>Authority to add, edit, and remove configurations of WireGuard instances.</p>
<h5>Administrator</h5>
<p>Full access across the system. Can view and modify all settings, configurations and manage users. </p>
2025-08-12 08:54:05 -03:00
<br>
<h4>Peer Groups</h4>
<p>Select which peer groups this user can access. If no peer groups are selected, the user will have access to all peers.</p>
<h4>Console</h4>
2025-12-29 18:30:39 -03:00
<p>Enable or disable web console access for this user.</p>
2026-01-16 15:01:13 -03:00
<h4>Enhanced Filter</h4>
<p>This option filters the API status response to include only peers that the user has access to. Depending on the size of your environment, enabling this option may impact performance. To mitigate this, consider increasing the "Web Refresh Interval" to reduce the number of requests.</p>
<h5>API Keys</h5>
<p>API Keys allow external applications to interact with the WireGuard WebAdmin API.</p>
<p><strong>Token:</strong> The secret token used for authentication. Keep this secure.</p>
<p><strong>Allowed Instances:</strong> The WireGuard instances this key can manage. If none are selected, the key has access to ALL instances.</p>
<p><strong>Permissions:</strong> specific actions allowed for this key.</p>
<h5>Application Route</h5>
<p>A Route defines a path prefix within this Application that requires a specific Access Policy.</p>
<ul>
<li><strong>Route Name</strong>: An internal identifier for this route (e.g., "public_api", "admin_area"). Used for reference and exports.</li>
<li><strong>Path Prefix</strong>: The URL path that triggers this route (e.g., <code>/api/</code> or <code>/admin/</code>). Use <code>/</code> to match all remaining paths.</li>
<li><strong>Policy</strong>: The Access Policy that will be enforced when a user accesses this path.</li>
<li><strong>Order</strong>: Determines the priority of this route when evaluating the request. Lower numbers are evaluated first. If multiple routes match a path, the one with the lowest order wins.</li>
</ul>
<h5>Application</h5>
<p>Define the main details of the application you want to expose through the gateway.</p>
<ul>
<li><strong>Name</strong>: A unique internal identifier for this application (e.g., "wiki", "crm"). Contains only letters, numbers, hyphens, or underscores.</li>
2026-11-20 21:58:17 -03:00
<li><strong>Display Name</strong>: A friendly, human-readable name for display purposes.</li>
<li><strong>Upstream</strong>: The destination URL where requests will be forwarded (e.g., <code>http://10.188.18.27:3000</code>). Must start with <code>http://</code> or <code>https://</code>.</li>
</ul>
<h5>Cluster Enabled</h5>
<p>When disabled, workers are refused and shut down their WireGuard interfaces, and App Gateway applications are only published by this primary server. Requires the WireGuard status cache.</p>
<h5>Primary Enable WireGuard</h5>
<p>Lists this primary server as an option when downloading peer configurations and VPN invites.</p>
<h5>Cluster Mode</h5>
<p><strong>Mirror</strong>: every worker receives the same WireGuard instances, peers, firewall and DNS configuration. Peers can connect to any server.</p>
<p><strong>Distributed</strong>: each WireGuard instance runs only on the server selected in the instance settings (the primary server by default). Peers connect to that server. Firewall rules cannot be bound to a specific instance interface: use wg+ or IP addresses. After changing the mode, apply the WireGuard configuration so the primary server stops the instances that moved to workers.</p>
<h5>Worker Display</h5>
<p>How workers are named in server selections (peer configuration downloads and VPN invites).</p>
<h5>IP Address List</h5>
<p>Manage specific IP addresses or networks that are allowed or denied access when using the IP Address List authentication method.</p>
<h5>IP Address & Prefix</h5>
<p>Enter a single IP address (e.g., 192.168.1.50) or a network address. Use the prefix length for CIDR notation (e.g., 24 for a /24 network). Leave prefix blank for a single host (/32 for IPv4, /128 for IPv6).</p>
<h5>Action</h5>
<p><strong>Allow</strong>: Grants access to the specified IP/network.<br>
<strong>Deny</strong>: Specifically blocks access from the specified IP/network.</p>
2025-08-12 08:54:05 -03:00
<h5>Description</h5>
2026-11-20 21:58:17 -03:00
<p>An optional note to help identify this entry (e.g., "Office Network", "Blocked Attacker").</p>
2025-08-12 08:54:05 -03:00
<h5>Peers</h5>
<p>Select which peers can be managed by users with this peer group.</p>
<h5>WireGuard Instances</h5>
2026-11-20 21:58:17 -03:00
<p>All peers in this WireGuard instance can be managed by users with this peer group, including adding or removing peers.</p>
<h5>Routing Templates</h5>
<p>Define routing configurations that can be applied to peers.</p>
<h5>Default Template</h5>
<p>If checked, this template will be the default for the selected WireGuard instance. Only one default template is allowed per instance.</p>
<h5>Route Type</h5>
<p>Select the type of routes to push to the client.</p>
2025-08-12 08:54:05 -03:00
<ul>
<li><strong>Default Route (0.0.0.0/0)</strong>: Redirects all traffic through the VPN.</li>
<li><strong>Routes from Peers on same Interface</strong>: Pushes routes for other peers on the same WireGuard interface.</li>
<li><strong>Routes from All Peers</strong>: Pushes routes for all peers across all interfaces.</li>
<li><strong>Custom Routes</strong>: Allows you to specify custom CIDR ranges.</li>
</ul>
<h5>Custom Routes</h5>
<p>Enter custom routes in CIDR notation, one per line (e.g., 192.168.1.0/24).</p>
<h5>Allow Peer Custom Routes</h5>
<p>If checked, allows specific peers to add their own custom routes on top of this template.</p>
<h5>Enforce Route Policy</h5>
<p>If enabled, firewall rules will be applied to strictly enforce this routing policy.<br>The peer will only be able to access networks explicitly defined by the assigned routing template.<br>Any traffic to destinations outside these routes will be blocked.</p>
<p>Note: depending on the number of routes and peers, enabling this option may generate a large number of firewall rules.</p>
<h5>Worker</h5>
<p>A worker is a cluster node that replicates WireGuard, firewall and DNS from this primary server and, optionally, publishes App Gateway applications.</p>
<h5>Name and location</h5>
<p>Used to identify the worker. The <strong>hostname</strong> is the address clients use to connect to this worker: it is written as the endpoint of the peer configurations downloaded for this server.</p>
<h5>Token</h5>
<p>Secret used by the worker to authenticate with this primary server. Changing it disconnects the worker until its configuration is updated.</p>
<h5>IP lock</h5>
<p>When enabled, the worker is only accepted from the IP address below. Without it, the address is updated automatically from the last connection.</p>
2026-01-27 15:22:12 -03:00
<h5>Enabled</h5>
<p>Disabled workers are refused and shut down their WireGuard interfaces until enabled again.</p>
<h5>Certificate</h5>
<p>Defines how the TLS certificate for this hostname is issued.</p>
<ul>
<li><strong>Trusted certificate (HTTP validation)</strong>: Issued through ACME (e.g. Let's Encrypt) and validated over HTTP. The hostname must point to this server and ports 80/443 must be reachable from the internet.</li>
<li><strong>Trusted certificate (DNS validation)</strong>: Issued through ACME and validated with a DNS record created using the selected DNS credential. The server does not need to be reachable from the internet.</li>
<li><strong>Self-signed certificate</strong>: Issued by the internal Caddy CA. Browsers will show a security warning.</li>
</ul>
<p>When the fallback option is enabled and a trusted certificate cannot be issued, a self-signed certificate is used until the next successful attempt. Without the fallback, the connection fails until the certificate is issued.</p>
<p>Use <strong>Retry certificate</strong> in the host list to request a new attempt right away, for example after fixing the DNS or firewall.</p>
<p><strong>Important:</strong> the certificate is requested as soon as the configuration is applied. With HTTP validation, the hostname must already point to this server: failed attempts count towards the Let's Encrypt limit (5 per hour per hostname). If the DNS is not ready yet, use DNS validation.</p>
'%(line)s' is not a network address. Use the network address (e.g., '%(net)s').(Share this password via a separate secure channel)<h2>Welcome to Your VPN Setup</h2>
<p>Begin by downloading the WireGuard app for your device using one of the links below.</p>
<p>Once installed, you can either <strong>scan the QR code</strong> or <strong>download the configuration file</strong> to quickly import your settings and start using your secure VPN connection.</p>A DNS credential can only be used with the DNS validation.A new certificate will be requested for %(hostname)s. The current configuration was exported.A peer can have only one IP with priority zero.A peer group with that name already exists.A worker with that name already exists.ACCEPTAPI DocumentationAPI Key deleted successfully.API Key saved successfully.API KeysAPI TokenAccess DeniedAccess PasswordAccess PoliciesAccess Policy deleted successfully.Access Policy saved successfully.ActionActionsActiveAddAdd API KeyAdd Access PolicyAdd Allowed DomainAdd Allowed EmailAdd ApplicationAdd Application HostAdd Application RouteAdd Auth MethodAdd Client routeAdd DNS CredentialAdd Filter ListAdd Forward Rule (allow)Add GroupAdd HostAdd IP AddressAdd IntervalAdd Peer GroupAdd ProfileAdd RouteAdd Routing TemplateAdd Time IntervalAdd UserAdd WireGuard InstanceAdd WorkerAddressAdministratorAllAll DNS queries will be forwarded to the primary resolver. If the primary resolver is not available, the secondary resolver will be used.AllowAllow ExportAllow ForwardAllow Instance to InstanceAllow Peer Custom RoutesAllow Peer to PeerAllow ReloadAllow RestartAllow access to everyone without authentication.Allow invalid or self-signed TLS certificates from the upstreamAllow invalid/self-signed certificateAllow traffic from VPN to WANAllowed Domain deleted successfully.Allowed Domain saved successfully.Allowed Email deleted successfully.Allowed Email saved successfully.Allowed Emails & DomainsAllowed GroupsAllowed IP or NetworkAllowed IPsAllowed InstancesAllowedIPs at Peer section of wgAllowedIPs at client configuration fileAllowing peer custom routes is not applicable when Route Type is 'Default Route'.App GatewayApplicationApplication Default Policy deleted successfully.Application Default Policy saved successfully.Application DetailsApplication Host deleted successfully.Application Host saved successfully.Application HostsApplication Route deleted successfully.Application Route saved successfully.Application RoutesApplication deleted successfully.Application saved successfully.ApplicationsApplications published by workers must use DNS validation or self-signed certificates: certificates are issued by this primary server and distributed to the workers.Applications served by cluster workers require DNS validation or self-signed certificates. Change the certificate of these hosts first: %(hosts)sApplyApply Route TemplateApply templateAre you sure you want to create a new peer?Are you sure you want to delete the API Key "%(name)s"?Are you sure you want to delete the DNS credential "%(name)s"?Are you sure you want to delete the IP address "%(address)s"?Are you sure you want to delete the access policy "%(name)s"?Are you sure you want to delete the allowed domain "%(domain)s"?Are you sure you want to delete the allowed email "%(email)s"?Are you sure you want to delete the application "%(name)s"?Are you sure you want to delete the authentication method "%(name)s"?Are you sure you want to delete the group "%(name)s"?Are you sure you want to delete the host "%(hostname)s"?Are you sure you want to delete the profile "%(name)s"?Are you sure you want to delete the route "%(name)s" (%(path)s)?Are you sure you want to delete the user "%(username)s"?Are you sure you want to delete this time interval?Are you sure you want to regenerate the token? The old token will stop working immediately.Are you sure you want to remove the default policy for "%(name)s"?At least one address does not appear in the wg show command output, which may indicate that another peer is using an overlapping IP or that the configuration file is outdated.At least one route must be provided when Route Type is 'Custom'.At least one user group must be selected when using Local Password
You're invited to join our secure WireGuard VPN network. Please click the link below to access your personalized VPN configuration:
{invite_url}
Note: This invitation link will expire in {expire_minutes} minutes. If you need a new link after expiration, please request another invite.Hide extrasHostHostnameHostname contains invalid characters.HostsHour(s)IP AddressIP Address ListIP Address cannot be used without selecting a WireGuard instance.IP Address deleted successfully.IP Address is required when IP Lock is enabled.IP Address saved successfully.IP AddressesIP LockIP Lock EnabledIP address added|IP address added successfully.IP address deleted|IP address deleted successfully.IP address updated|IP address updated successfully.IP addresses can only use a self-signed certificate.IP lock is enabled, but the worker is attempting to access from a different IP address.IdentityIf you find any issues with the translation or would like to request a new language, please open anInIn InterfaceInactiveInstallationInstanceInstance IDInstance TrafficInterfaceInterface KeysInternal IP AddressInternal NetworkInvalidInvalid Destination. Either Peer or IP Address must be informed.Invalid TOTP PIN.Invalid TOTP secret format. Must be a valid Base32 string.Invalid action.Invalid commandInvalid config fileInvalid confirmation|Please confirm deletion of WireGuard instance: wgInvalid hostname or IP AddressInvalid hostname.Invalid route format: '%(line)s'. Please use CIDR notation (e.g., 10.0.0.0/24).Invalid search domain: %(domain)sInvalid targetInvite SettingsInvite Settings|Settings saved successfully.Invite URLInvite URL must end with '/invite/'.Invite URL must start with 'https://'.Invite data is not available.Invite refreshed.Invite text copied to clipboard.KeysLanguageLast SeenLast UpdateLast reported stateLast updateLatest HandshakeLeave blank to keep the current value (ending in %(suffix)s).Leave this empty when the application is served on all cluster workers.LettersLetters, DigitsLetters, Digits, Special CharactersLinked Peers (Debug)List Peer GroupsList URLList UsersListen PortLocal PasswordLocationLoginLogin againMASQUERADEMain ip addressManageManage Firewall RuleManage Firewall SettingsManage IP address or NetworkManage Peer Schedule ProfileManage Port ForwardManage client routeMasquerade SourceMasquerade traffic from VPN to WANMaster Cache Processing TimeMembersMemory usageMessage templatesMinimum 8 characters, with at least one uppercase letter, one lowercase letter, and one number.Missing a method or feature?MondayNameNeed attentionNetmaskNeverNewNew WireGuard InstanceNext DisableNext EnableNext disableNext enableNoNo Access Policies found.No Allowed Emails or Domains found.No Applications found.No Authentication Methods found.No DNS Credentials found.No Gatekeeper Groups found.No Gatekeeper Users found.No Hosts configured for this application.No Hosts found.No IP Addresses found.No Routes configured for this application.No WireGuard Instances FoundNo WireGuard instancesNo WireGuard instances found.No active VPN invitationsNo certificate is being served for this hostname.No interfaces found|No WireGuard interfaces were found to process.No invite data available to refresh.No peers linked to this profile.No profile associatedNo recent report from this server.No report received yet.No routing templates available for this interface.No schedule profiles found.No time intervals found.No traffic history, please wait a few minutesNo workers configuredNot DestinationNot SourceNot StateNot installedNot setOIDC Client IDOIDC Client SecretOIDC Provider URLOIDC authentication is temporarily unavailable and will be available soon.OIDC fields must be empty for Local Password authentication.OIDC fields must be empty for TOTP authentication.OfflineOne route per line in CIDR notation.One-Time Password (TOTP)OnlineOnly one Local Password authentication method can be configured.Open an issue on GitHubOpenID Connect (OIDC)Optional. One or more domains separated by commas (e.g. vpn, example.com).OrderOutOut InterfacePacket StateParameters
Report-Msgid-Bugs-To:
PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: LANGUAGE <LL@li.org>
Language:
2025-08-12 08:54:05 -03:00
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n == 1 ? 0 : n % 1 == 0 && n >= 2 && n <= 4 ? 1 : n % 1 != 0 ? 2: 3);
<h5>Pokro�ilá konfigurácia VPN firewall</h5>
<p>
Toto rozhranie slúži ako komplexný nástroj na správu firewall pravidiel, umož�ujúci používateľom implementovať pokro�ilé politiky komunikácie medzi VPN peermi a sieťami. Zjednodušuje vytváranie firewall pravidiel, filtrovanie paketov a NAT konfigurácie, umož�ujúc presný kontrol nad sieťovou bezpe�nosťou. Používatelia môžu definovať zdrojové a cieľové IP adresy, porty, protokoly a akcie na prispôsobenie toku komunikácie, zabezpe�ujúc bezpe�né a efektívne sieťové prostredie.
</p>
<h5>VΓ½ber cieΔΎa</h5>
2026-03-13 20:44:45 -03:00
<p>
MΓ΅te moΕΎnosΕ¥ aplikovaΕ¥ toto pravidlo na Ε΅pecifickΓΊ IP adresu alebo sieΕ¥ a/alebo na viacero peerov ako cieΔΎ.<br><br>
Povolenie moΕΎnosti "ZahrnΓΊΕ¥ peer siete" automaticky zahrnie vΕ΅etky povolenΓ© IP adresy spojenΓ© s kaΕΎdΓ½m vybranΓ½m peerom ako cieΔΎ.<br><br>
Prosím všimnite si, že výber viacerých peerov so zahrnutými sieťami na strane zdroja aj cieľa môže viesť k rýchlemu nárastu po�tu vygenerovaných firewall pravidiel, v závislosti od vašej konfigurácie.<br><br>
MoΕΎnosΕ¥ "Nie cieΔΎ" neguje vybranΓ½ cieΔΎovΓ½ IP, sieΕ¥ alebo peer(y).
</p>
<h5>Protokol a port</h5>
<p>
Tu sú uvedené len naj�astejšie používané protokoly. Ak potrebujete špecifický protokol, prosím otvorte issue na GitHub.<br><br>
VΓ½ber TCP+UDP bude maΕ¥ za nΓ΅sledok duplikΓ΅ciu vygenerovanΓ½ch pravidiel.<br><br>
Porty mΓ΄ΕΎu byΕ¥ Ε΅pecifikovanΓ© ako jednotlivΓ© Δ�Γ­sla (napr. 8080) alebo ako rozsahy (napr. 8001:8999).
</p>
2026-11-17 16:03:37 -03:00
<h5>VΓ½ber zdroja</h5>
<p>
MΓ΅te moΕΎnosΕ¥ aplikovaΕ¥ toto pravidlo na Ε΅pecifickΓΊ IP adresu alebo sieΕ¥ a/alebo na viacero peerov.<br><br>
Povolenie moΕΎnosti "ZahrnΓΊΕ¥ peer siete" automaticky zahrnie vΕ΅etky povolenΓ© IP adresy spojenΓ© s kaΕΎdΓ½m vybranΓ½m peerom.<br><br>
2026-03-18 11:24:10 -03:00
Prosím všimnite si, že výber viacerých peerov so zahrnutými sieťami na strane zdroja aj cieľa môže viesť k rýchlemu nárastu po�tu vygenerovaných firewall pravidiel, v závislosti od vašej konfigurácie.<br><br>
MoΕΎnosΕ¥ "Nie zdroj" neguje vybranΓΊ zdrojovΓΊ IP, sieΕ¥ alebo peer(y).
</p>
DNS servery odoslanΓ© peerom.
<br>
PouΕΎitie internej IP ako primΓ΅rneho DNS umoΕΎΕ�uje internΓ© rozlΓ­Ε΅enie nΓ΅zvov
a filtrovanie DNS.
Vynucuje smerovacie pravidlΓ΅ definovanΓ© smerovacΓ­mi Ε΅ablΓ³nami pomocou pravidiel firewallu.
<br>
Peeri s predvolenou trasou (0.0.0.0/0) nie sΓΊ obmedzenΓ­.
2026-03-15 17:31:19 -03:00
<br><br>
Poznámka: v závislosti od po�u trás a peerov môže táto možnosť vygenerovať
veľký po�et pravidiel firewallu.
InternΓ΅ IP adresa a sieΕ¥ovΓ΅ maska pouΕΎΓ­vanΓ΅ rozhranΓ­m WireGuard.
Interval pouΕΎΓ­vanΓ½ na obnovenie informΓ΅ciΓ­ o stave WireGuard vo webovom pouΕΎΓ­vateΔΎskom rozhranΓ­.
VoliteΔΎnΓ½ nΓ΅zov pouΕΎΓ­vanΓ½ iba na zobrazenie vo webovom rozhranΓ­.
VerejnΓ½ nΓ΅zov hostiteΔΎa alebo IP adresa a UDP port, ktorΓ½ pouΕΎΓ­vajΓΊ peeri na pripojenie.
<br>
<b>Port po�úvania</b> musí byť sprístupnený a namapovaný vo vašom súbore Docker compose (YAML).
2025-08-12 08:54:05 -03:00
SΓΊkromnΓ© a verejnΓ© kΔΎΓΊΔ�e WireGuard pre toto rozhranie.
<br>
SΓΊkromnΓ½ kΔΎΓΊΔ� musΓ­ zostaΕ¥ v tajnosti.
Jeho zmena vyΕΎaduje aktualizΓ΅ciu konfigurΓ΅ciΓ­ vΕ΅etkΓ½ch peerov.
<h5>PredvolenΓ© porty</h5>
<p>PredvolenΓ½ <code>docker-compose.yml</code> sΓΊbor Ε΅pecifikuje <b>TCP</b> rozsah portov <b>8080-8089</b>. Ak si ΕΎelΓ΅te zmeniΕ¥ presmerovanie portov na inΓ½ rozsah, musΓ­te manuΓ΅lne upraviΕ¥ <code>docker-compose.yml</code> sΓΊbor a znovu spustiΕ¥ Docker Compose krok uvedenΓ½ v <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">pokynoch na nasadenie</a>.</p>
<h5>Typ cieΔΎa: Peer</h5>
<p>Presmerovanie portov bude uprednost�ovať prvú IP adresu peer s prioritou nula.</p>
<h5>Typ cieΔΎa: IP adresa</h5>
<p>PravidlΓ΅ presmerovania portov budΓΊ presmerovΓ΅vaΕ¥ na Ε΅pecifikovanΓΊ IP adresu. Nezabudnite prideliΕ¥ IP adresu alebo sieΕ¥ peer.</p>
<h5>PridΓ΅vanie pravidla presmerovania</h5>
<p>Automaticky generuje pravidlo presmerovania pre prispΓ΄sobenie prΓ­snejΕ΅Γ­ch nastavenΓ­ firewall.</p>
<h5>Maskovanie zdroja</h5>
<p>Toto slúži ako do�asné riešenie ke� peer nepoužíva VPN ako svoju predvolenú bránu. Je dôležité poznamenať, že táto konfigurácia nie je odporú�aná, pretože mení zdrojovú adresu všetkých pripojení tak, aby zodpovedala IP adrese WireGuard inštancie.</p>
<h5>Politika odmietnutia</h5>
<p>Politika odmietnutia blokuje vΕ΅etok prΓ­stup k zodpovedajΓΊcim trasΓ΅m.</p>
<h5>ChrΓ΅nenΓ΅ politika</h5>
<p>ChrΓ΅nenΓ΅ politika vyΕΎaduje, aby sa pouΕΎΓ­vatelia pred prΓ­stupom k aplikΓ΅cii overili.</p>
<ul>
<li><strong>Povolené skupiny</strong>: Obmedzuje prístup pre konkrétne skupiny používateľov. Poznámka: Používanie skupín vyžaduje výber autentifika�nej metódy typu �Miestne heslo�.</li>
<li><strong>Autentifika�né metódy</strong>: Špecifikujte, ktoré metódy môžu používatelia použiť na overenie (napr. miestne heslo, TOTP, OIDC).</li>
</ul>
2026-02-09 22:07:48 -03:00
<h5>VerejnΓ΅ politika</h5>
<p>VerejnΓ΅ politika umoΕΎΕ�uje prΓ­stup k aplikΓ΅cii bez vyΕΎadovania akΓ©hokoΔΎvek overenia.</p>
<div class="alert alert-warning">
Tento nΓ΅zov hostiteΔΎa sa pouΕΎΓ­va na prΓ­stup k WireGuard WebAdmin. Ak certifikΓ΅t nie je moΕΎnΓ© vydaΕ¥,
2025-12-29 18:30:39 -03:00
váš prehliada� bude zobrazovať bezpe�nostné upozornenie, kým sa problém neodstráni.
2026-03-12 18:54:37 -03:00
</div>
<h4>Typy autentifikΓ΅cie</h4>
<p>Vyberte, ako sa budΓΊ pouΕΎΓ­vatelia overovaΕ¥ pomocou tejto metΓ³dy.</p>
<h5>LokΓ΅lne heslo</h5>
<p>PouΕΎΓ­vatelia sa budΓΊ overovaΕ¥ pomocou Ε΅tandardnΓ©ho pouΕΎΓ­vateΔΎskΓ©ho mena a hesla uloΕΎenΓ©ho lokΓ΅lne. Je moΕΎnΓ© vytvoriΕ¥ iba jednu metΓ³du tohto typu.</p>
<h5>OIDC (OpenID Connect)</h5>
2026-03-13 20:44:45 -03:00
<p>PouΕΎΓ­vatelia sa budΓΊ overovaΕ¥ prostrednΓ­ctvom externΓ©ho poskytovateΔΎa identity (naprΓ­klad Keycloak alebo Google). VyΕΎaduje URL poskytovateΔΎa, ID klienta a tajnΓ½ kΔΎΓΊΔ� klienta.</p>
<h5>TOTP (Δ�asovo zaloΕΎenΓ© jednorazovΓ© heslo)</h5>
<p>Používatelia budú musieť zadať rotujúci token z autentifika�nej aplikácie. Ak používateľ nemá nakonfigurované osobné TOTP, namiesto toho sa použije <strong>globálne tajomstvo TOTP</strong>. </p>
<h4>PouΕΎΓ­vateΔΎ Gatekeeper</h4>
<p>Používatelia Gatekeeper sa používajú na autentifikáciu vo�i chráneným aplikáciám spravovaným touto bránou.</p>
2026-11-20 21:58:17 -03:00
<h5>Heslo</h5>
<p>VyΕΎaduje sa pri vytvΓ΅ranΓ­ pouΕΎΓ­vateΔΎa. Pri ΓΊprave ponechajte obe polia pre heslo prΓ΅zdne, aby sa zachovalo aktuΓ΅lne heslo.
HeslΓ΅ sa ukladajΓΊ pomocou haΕ΅ovania <strong>Argon2id</strong>.</p>
<h5>TOTP tajomstvo</h5>
<p>Voliteľné TOTP tajomstvo pre konkrétneho používateľa. Ke� je nastavené, tento používateľ sa bude autentifikovať pomocou vlastného tajomstva namiesto
globálneho TOTP tajomstva konfigurovaného v metóde autentifikácie. Pomocou tla�idiel pod poľom vygenerujte
nΓ΅hodnΓ© tajomstvo a naskenujte QR kΓ³d pomocou vaΕ΅ej aplikΓ΅cie autentifikΓ΅tora. Pred uloΕΎenΓ­m overte tajomstvo zadanΓ­m aktuΓ΅lneho
6-miestneho kΓ³du PIN.</p>
<h4>Γ�rovne pouΕΎΓ­vateΔΎov</h4>
<h5>Analytik ladenia</h5>
<p>PrΓ­stup k zΓ΅kladnΓ½m systΓ©movΓ½m informΓ΅ciΓ΅m a logom na rieΕ΅enie problΓ©mov. Ε½iadny prΓ­stup na ΓΊpravu nastavenΓ­ alebo zobrazenie citlivΓ½ch ΓΊdajov ako sΓΊ kΔΎΓΊΔ�e peerov.</p>
2026-03-12 18:54:37 -03:00
<h5>Len na prezeranie</h5>
<p>Plný prístup na prezeranie vrátane kľú�ov peerov a konfigura�ných súborov. Nemôže upravovať žiadne nastavenia alebo konfigurácie.</p>
<h5>SprΓ΅vca peer</h5>
<p>Oprávnenia na pridávanie, upravovanie a odstra�ovanie peerov a IP adries. Nezahŕ�a prístup na úpravu konfigurácií WireGuard inštancií alebo nastavení vyššej úrovne.</p>
<h5>SprΓ΅vca WireGuard</h5>
<p>Oprávnenie na pridávanie, upravovanie a odstra�ovanie konfigurácií WireGuard inštancií.</p>
<h5>AdministrΓ΅tor</h5>
<p>PlnΓ½ prΓ­stup k celΓ©mu systΓ©mu. MΓ΄ΕΎe zobrazovaΕ¥ a upravovaΕ¥ vΕ΅etky nastavenia, konfigurΓ΅cie a spravovaΕ¥ pouΕΎΓ­vateΔΎov.</p>
2025-08-12 08:54:05 -03:00
<br>
<h4>Peer skupiny</h4>
<p>Vyberte ktorΓ© peer skupiny mΓ΄ΕΎe tento pouΕΎΓ­vateΔΎ pristupovaΕ¥. Ak nie sΓΊ vybranΓ© ΕΎiadne peer skupiny, pouΕΎΓ­vateΔΎ bude maΕ¥ prΓ­stup ku vΕ΅etkΓ½m peerom.</p>
<h4>Konzola</h4>
2025-12-29 18:30:39 -03:00
<p>PovoliΕ¥ alebo zakΓ΅zaΕ¥ prΓ­stup k webovej konzole pre tohto pouΕΎΓ­vateΔΎa.</p>
2026-01-16 15:01:13 -03:00
<h4>RozΕ΅Γ­renΓ½ filter</h4>
<p>Táto možnosť filtruje odpove� API stavu tak, aby zahŕ�ala len peerov, ku ktorým má používateľ prístup. V závislosti od veľkosti vášho prostredia môže povolenie tejto možnosti ovplyvniť výkon. Na zmiernenie zvážte zvýšenie "Intervalu obnovenia webu" na zníženie po�tu požiadaviek.</p>
<h5>KΔΎΓΊΔ�e API</h5>
<p>KΔΎΓΊΔ�e API umoΕΎΕ�ujΓΊ externΓ½m aplikΓ΅ciΓ΅m komunikovaΕ¥ s API WireGuard WebAdmin.</p>
<p><strong>Token:</strong> Tajný token používaný na autentifikáciu. Uchovávajte ho v bezpe�í.</p>
<p><strong>Povolené inštancie:</strong> Inštancie WireGuard, ktoré tento kľú� môže spravovať. Ak nie sú vybrané žiadne, kľú� má prístup ku VŠETK�M inštanciám.</p>
<p><strong>Povolenia:</strong> Ε΅pecifickΓ© akcie povolenΓ© pre tento kΔΎΓΊΔ�.</p>
<h5>Trasa aplikΓ΅cie</h5>
<p>Trasa definuje prefix cesty v rΓ΅mci tejto aplikΓ΅cie, ktorΓ½ vyΕΎaduje Ε΅pecifickΓΊ politiku prΓ­stupu.</p>
<ul>
<li><strong>Názov trasy</strong>: Interný identifikátor pre túto trasu (napr. �public_api�, �admin_area�). Používa sa na referenciu a exporty.</li>
<li><strong>Prefix cesty</strong>: Cesta URL, ktorΓ΅ spΓΊΕ΅Ε¥a tΓΊto trasu (napr. <code>/api/</code> alebo <code>/admin/</code>). PouΕΎite <code>/</code> na zhodu so vΕ΅etkΓ½mi zostΓ΅vajΓΊcimi cestami.</li>
<li><strong>Politika</strong>: Politika prístupu, ktorá sa vynúti, ke� používateľ pristúpi k tejto ceste.</li>
<li><strong>Poradie</strong>: Ur�uje prioritu tejto trasy pri vyhodnocovaní požiadavky. Nižšie �ísla sa vyhodnocujú ako prvé. Ak sa s cestou zhoduje viacero trás, vyhráva tá s najnižším poradím.</li>
</ul>
<h5>AplikΓ΅cia</h5>
<p>Definujte hlavnΓ© podrobnosti aplikΓ΅cie, ktorΓΊ chcete vystaviΕ¥ prostrednΓ­ctvom brΓ΅ny.</p>
<ul>
<li><strong>Názov</strong>: Jedine�ný interný identifikátor pre túto aplikáciu (napr. �wiki�, �crm�). Obsahuje iba písmená, �ísla, poml�ky alebo pod�iarkovníky.</li>
2026-11-20 21:58:17 -03:00
<li><strong>ZobrazenΓ½ nΓ΅zov</strong>: PriateΔΎskΓ½, Δ�itateΔΎnΓ½ nΓ΅zov na ΓΊΔ�ely zobrazenia.</li>
<li><strong>Upstream</strong>: Cieľová URL adresa, kam sa budú požiadavky presmerovávať (napr. <code>http://10.188.18.27:3000</code>). Musí za�ínať na <code>http://</code> alebo <code>https://</code>.</li>
</ul>
<h5>Cluster povolenΓ½</h5>
<p>Ak je zakΓ΅zanΓ½, workery sΓΊ odmietnutΓ© a vypnΓΊ svoje rozhrania WireGuard a aplikΓ΅cie App Gateway publikuje iba tento primΓ΅rny server. VyΕΎaduje cache stavu WireGuard.</p>
<h5>PrimΓ΅rne povolenie WireGuard</h5>
<p>PonΓΊkne tento primΓ΅rny server ako moΕΎnosΕ¥ pri sΕ¥ahovanΓ­ konfigurΓ΅ciΓ­ peerov a VPN pozvΓ΅nok.</p>
<h5>ReΕΎim clustra</h5>
<p><strong>Mirror</strong>: kaΕΎdΓ½ worker dostane rovnakΓ© inΕ΅tancie WireGuard, peerov, firewall a konfigurΓ΅ciu DNS. Peeri sa mΓ΄ΕΎu pripojiΕ¥ k ΔΎubovoΔΎnΓ©mu serveru.</p>
<p><strong>Distributed</strong>: kaΕΎdΓ΅ inΕ΅tancia WireGuard beΕΎΓ­ iba na serveri vybranom v nastaveniach inΕ΅tancie (predvolene na primΓ΅rnom serveri). Peeri sa pripΓ΅jajΓΊ k tomuto serveru. PravidlΓ΅ firewallu nemΓ΄ΕΎu byΕ¥ viazanΓ© na rozhranie konkrΓ©tnej inΕ΅tancie: pouΕΎite wg+ alebo IP adresy. Po zmene reΕΎimu aplikujte konfigurΓ΅ciu WireGuard, aby primΓ΅rny server zastavil inΕ΅tancie presunutΓ© na workery.</p>
<h5>Zobrazenie workera</h5>
<p>Ako sa workery zobrazujΓΊ pri vΓ½bere servera (sΕ¥ahovanie konfigurΓ΅ciΓ­ peerov a VPN pozvΓ΅nky).</p>
<h5>Zoznam IP adries</h5>
<p>Spravujte konkrΓ©tne IP adresy alebo siete, ktorΓ½m je povolenΓ½ alebo odmietnutΓ½ prΓ­stup pri pouΕΎΓ­vanΓ­ metΓ³dy autentifikΓ΅cie pomocou zoznamu IP adries.</p>
<h5>IP adresa a prefix</h5>
<p>Zadajte jednu IP adresu (napr. 192.168.1.50) alebo sieΕ¥ovΓΊ adresu. PouΕΎite dΔΊΕΎku prefixu pre notΓ΅ciu CIDR (napr. 24 pre sieΕ¥ /24). Ponechajte prefix prΓ΅zdny pre jednΓ©ho hostiteΔΎa (/32 pre IPv4, /128 pre IPv6).</p>
<h5>Akcia</h5>
<p><strong>PovoliΕ¥</strong>: UdeΔΎuje prΓ­stup k zadanej IP/sieti.<br>
<strong>OdmietnuΕ¥</strong>: Ε pecificky blokuje prΓ­stup zo zadanej IP/siete.</p>
2025-08-12 08:54:05 -03:00
<h5>Popis</h5>
2026-11-20 21:58:17 -03:00
<p>Voliteľná poznámka, ktorá pomôže identifikovať tento záznam (napr. �Kancelárska sieť�, �Blokovaný úto�ník�).</p>
2025-08-12 08:54:05 -03:00
<h5>Peeri</h5>
<p>Vyberte ktorΓ© peeri mΓ΄ΕΎu byΕ¥ spravovanΓ© pouΕΎΓ­vateΔΎmi s touto peer skupinou.</p>
<h5>WireGuard inΕ΅tancie</h5>
2026-11-20 21:58:17 -03:00
<p>Všetky peeri v tejto WireGuard inštancii môžu byť spravované používateľmi s touto peer skupinou, vrátane pridávania alebo odstra�ovania peerov.</p>