en	String found

en	String not found

en	Failed string found

en	Failed strint not found

en	Maint string found

en	Not tested yet

en	Search not performed

en	HTTP plaintext, default port 80

en	HTTP encrypted (HTTPS), default port 443

en	SMTP plaintext, default port 25 (or 587 for submission)

en	SMTP with STARTTLS, default port 25(or 587 for submission)

en	SMTP encrypted (SMTPS), default port 465

en	IMAP plaintext, default port 143

en	IMAP with STARTTLS, default port 143

en	IMAP encrypted (IMAPS), default port 993

en	POP3 plaintext, default port 110

en	POP3 with STARTTLS, default port 110

en	POP3 encrypted (POP3S), default port 995

en	DNS plaintext, default port 53

en	LDAP plaintext, default port 389

en	LDAP encrypted (LDAPS), default port 636

en	FTP plaintext, default port 21

en	FTP encrypted (FTPS), default port 990

en	SCP download file, default port 22

en	TFTP protocol - download file, default port 69

en	SMB plaintext download file, default port 445

en	SMB encrypted (SMBS) download file, default port 445

en	Last hour

en	Last 6 hours

en	Last day

en	Last week

en	Unable to Connect

en	Continue

en	Switching Protocols

en	OK

en	Created

en	Accepted

en	Non-Authoritative Information

en	No Content

en	Reset Content

en	Partial Content

en	Multiple Choices

en	Moved Permanently

en	Found

en	See Other

en	Not Modified

en	Use Proxy

en	(Unused)

en	Temporary Redirect

en	Bad Request

en	Unauthorized

en	Payment Required

en	Forbidden

en	Not Found

en	Method Not Allowed

en	Not Acceptable

en	Proxy Authentication Required

en	Request Timeout

en	Conflict

en	Gone

en	Length Required

en	Precondition Failed

en	Request Entity Too Large

en	Request-URI Too Long

en	Unsupported Media Type

en	Requested Range Not Satisfiable

en	Expectation Failed

en	Internal Server Error

en	Not Implemented

en	Bad Gateway

en	Service Unavailable

en	Gateway Timeout

en	HTTP Version Not Supported

en	%d Poller run

en	%d Poller runs

en	%d Seconds

en	Delete

en	Disable

en	Enable

en	Duplicate

en	Name

en	A Useful Name for this CA chain.

en	New CA

en	CA Chain

en	CA and intermediate certs, PEM encoded

en	A Useful Name for this Proxy.

en	New Proxy

en	Hostname

en	The Proxy Hostname.

en	HTTP Port

en	The HTTP Proxy Port.

en	HTTPS Port

en	The HTTPS Proxy Port.

en	User Name

en	The user to use to authenticate with the Proxy if any.

en	Password

en	The user password to use to authenticate with the Proxy if any.

en	General Settings

en	Service Check Name

en	The name that is displayed for this Service Check, and is included in any Alert notifications.

en	Enable Service Check

en	Uncheck this box to disabled this test from being checked.

en	Poller

en	Poller on which the test will run

en	Type of service

en	What type of service?

en	IP Address or DNS name of server

en	You can specify another port (example.com:5000) otherwise default will be used

en	Service settings

en	None

en	Your own CA and intermediate certs

en	Username

en	With authentication the test gains more information. For LDAP something like cn=John Doe,OU=anygroup,DC=example,DC=com. For smb use DOMAIN/user

en	For anonymous ftp insert email address here.

en	LDAP Search

en	LDAP search filter, it could be ,OU=anygroup,DC=example,DC=com

en	DNS Name for Query

en	DNS name for querying

en	Path Part of URL

en	For web service insert at least "/" or something like "/any/path/". For FTP listing must end with char "/". For TFTP/SCP/SMB download test insert /path/file

en	Requires Authentication

en	Check this box if the site will normally return a 401 Error as it requires a username and password.

en	Proxy Server

en	If this connection text requires a proxy, select it here. Otherwise choose 'None'.

en	Check Certificate

en	If using SSL, check this box if you want to validate the certificate. Default on, turn off if you the site uses a self-signed certificate.

en	Check and notify Certificate expiration

en	If using SSL, check this box if you want to check the certificate expiration. You will be warn when last 10 days left.

en	Notification Timing

en	How Often to Test

en	Test each poller cycle or less

en	Trigger

en	How many poller cycles must be down before it will send an alert. After an alert is sent, in order for a 'Site Recovering' Email to be send, it must also be up this number of poller cycles.

en	Time Out

en	How many seconds to allow the page to timeout before reporting it as down.

en	Verification Strings

en	Response Search String

en	This is the string to search for in the response for a live and working service.

en	Response Search String - Maintenance

en	This is the string to search for on the Maintenance . The Service Check will check for this string if the above string is not found. If found, it means that the service is under maintenance.

en	Response Search String - Failed

en	This is the string to search for a known failure in the service response. The Service Check will only alert if this string is found, ignoring any timeout issues and the search strings above.

en	Notification Settings

en	Notify Format

en	This is the format to use when sending the notification email

en	Notification List

en	Use this Notification List for those to be notified when this service goes down.

en	Notify Accounts

en	This is a listing of accounts that will be notified when this service goes down.

en	Extra Alert Emails

en	You may specify here extra Emails to receive alerts for this test (comma separated)

en	Notes

en	Notes sent in email

en	External ID

en	Enter an Eternal ID for this Thold Template.

en	All fine. Proceed as usual.

en	The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you did not use, it can be a misspelled protocol string or just a protocol libcurl has no code for.

en	Early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental could not get done at init time.

en	The URL was not properly formatted.

en	A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt libcurl.

en	Could not resolve proxy. The given proxy host could not be resolved.

en	Could not resolve host. The given remote host was not resolved.

en	Failed to connect() to host or proxy.

en	The server sent data libcurl could not parse. This error code was known as CURLE_FTP_WEIRD_SERVER_REPLY before 7.51.0.

en	We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.

en	While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.

en	After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected code was returned.

en	During an active FTP session while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired.

en	Libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. The server is flawed.

en	FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line, this return code is passed back.

en	An internal failure to lookup the host used for the new connection.

en	A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

en	Received an error when trying to set the transfer mode to binary or ASCII.

en	A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that does not match the previously given size.

en	This was either a weird reply to a 'RETR' command or a zero byte transfer complete.

en	Obsolete Error

en	Not used in modern versions.

en	When sending custom "QUOTE" commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command.

en	This is returned if CURLOPT_FAILONERROR is set true and the HTTP server returns an error code that is >= 400.

en	An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback.

en	Failed starting the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server's explanation for this.

en	There was a problem reading a local file or an error returned by the read callback.

en	A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs.

en	Operation timeout. The specified time-out period was reached according to the conditions.

en	The FTP PORT command returned error. This mostly happens when you have not specified a good enough address for libcurl to use. See CURLOPT_FTPPORT.

en	The FTP REST command returned error. This should never happen if the server is sane.

en	The server does not support or accept range requests.

en	This is an odd error that mainly occurs due to internal confusion.

en	A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.

en	The download could not be resumed because the specified offset was out of the file boundary.

en	A file given with FILE:// could not be opened. Most likely because the file path does not identify an existing file. Did you check file permissions?

en	LDAP cannot bind. LDAP bind operation failed.

en	LDAP search failed.

en	Function not found. A required zlib function was not found.

en	Aborted by callback. A callback returned "abort" to libcurl.

en	A function was called with a bad parameter.

en	Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections' source IP address with URLOPT_INTERFACE.

en	Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.

en	An option passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem in the program that uses libcurl. The error buffer might contain more specific information about which exact option it concerns.

en	An option passed in to a setopt was wrongly formatted. See error message for details about what option.

en	Nothing was returned from the server, and under the circumstances, getting nothing is considered an error.

en	The specified crypto engine was not found.

en	Failed setting the selected SSL crypto engine as default.

en	Failed sending network data.

en	Failure with receiving network data.

en	problem with the local client certificate.

en	Could not use specified cipher.

en	The remote server's SSL certificate or SSH fingerprint was deemed not OK. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.

en	Unrecognized transfer encoding.

en	Maximum file size exceeded.

en	Requested FTP SSL level failed.

en	When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation failed.

en	Initiating the SSL Engine failed.

en	The remote server denied curl to login (Added in 7.13.1)

en	File not found on TFTP server.

en	Permission problem on TFTP server.

en	Out of disk space on the server.

en	Illegal TFTP operation.

en	Unknown TFTP transfer ID.

en	File already exists and is not overwritten.

en	This error should never be returned by a properly functioning TFTP server.

en	Problem with reading the SSL CA cert (path? access rights?)

en	The resource referenced in the URL does not exist.

en	An unspecified error occurred during the SSH session.

en	Failed to shut down the SSL connection.

en	Socket is not ready for send/recv wait till it's ready and try again. This return code is only returned from curl_easy_recv and curl_easy_send (Added in 7.18.2)

en	Failed to load CRL file (Added in 7.19.0)

en	Issuer check failed (Added in 7.19.0)

en	The FTP server does not understand the PRET command at all or does not support the given argument. Be careful when using CURLOPT_CUSTOMREQUEST, a custom LIST command is sent with the PRET command before PASV as well. (Added in 7.20.0)

en	Mismatch of RTSP CSeq numbers.

en	Mismatch of RTSP Session Identifiers.

en	Unable to parse FTP file list (during FTP wildcard downloading).

en	Chunk callback reported error.

en	(For internal use only, is never returned by libcurl) No connection available, the session is queued. (added in 7.30.0)

en	Failed to match the pinned key specified with CURLOPT_PINNEDPUBLICKEY.

en	Status returned failure when asked with CURLOPT_SSL_VERIFYSTATUS.

en	Stream error in the HTTP/2 framing layer.

en	An API function was called from inside a callback.

en	An authentication function returned an error.

en	A problem was detected in the HTTP/3 layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

en	QUIC connection error. This error may be caused by an SSL library error. QUIC is the protocol used for HTTP/3 transfers.

en	Proxy handshake error. CURLINFO_PROXY_ERROR provides extra details on the specific problem.

en	SSL Client Certificate required.

en	An internal call to poll() or select() returned error that is not recoverable.

en	Tests

en	CA certificates

en	Proxies

en	Curl return codes

en	Log History

en	Graphs

en	No data

en	Click 'Continue' to delete the following CA.

en	Click 'Continue' to delete following CA.

en	Cancel

en	Delete CA

en	Delete CA

en	CA [edit: %s]

en	CA [new]

en	Used

en	CAs

en	No CAs Found

en	Servcheck CA Management

en	Servcheck uses a file of certificates from common root CAs to check certificates. This will work for certificates issued by common CAs. If you are using a custom CA (for example, in a Microsoft AD environment), the test for that certificate will fail because servcheck does not know your CA. You must upload the entire chain (CA certificate and intermediate certificates). You then associate these with the test where the certificate issued by your CA is.

en	Search

en	Default

en	Go

en	Clear

en	No error codes

en	Click 'Continue' to delete the following Proxy.

en	Click 'Continue' to delete following Proxies.

en	Delete Proxy

en	Delete Proxies

en	Proxy [edit: %s]

en	Proxy [new]

en	Ports (http/https)

en	Not Set

en	No Servers Found

en	Servcheck Proxy Management

en	Click 'Continue' to Delete the following tests.

en	Click 'Continue' to Delete following tests.

en	Delete rest

en	Delete tests

en	Click 'Continue' to Disable the following test.

en	Click 'Continue' to Disable following Tests.

en	Disable test

en	Disable Tests

en	Click 'Continue' to Enable the following test.

en	Click 'Continue' to Enable following tests.

en	Enable test

en	Enable tests

en	Click 'Continue' to Duplicate the following test.

en	Click 'Continue' to Duplicate following tests.

en	Duplicate test

en	Duplicate tests

en	The Service Check history was purged for %s

en	Query [edit: %s]

en	Query [new]

en	No Users Selected

en	Users Selected

en	All Users Selected

en	All

en	Date

en	Result

en	Search result

en	Curl return code

en	DNS

en	Connect

en	Redirect

en	Total

en	Service Down

en	Service UP

en	No Service Check Events in History

en	Last returned data of test

en	Actions

en	Enabled

en	Last Check

en	Stats (OK/problem)

en	Trigerred

en	Checks

en	Edit Service Check

en	Disable Service Check

en	View Service Check History

en	View Last returned data

en	View Graph

en	Disabled

en	N/A

en	No

en	Yes

en	No Tests Found

en	Service Checks

en	State

en	Any

en	Refresh

en	Service Check History

en	Date Search

en	Entries

en	Purge Events

en	Service Check Admin

en	Management

en	Service Checker

en	Service Check Edit

en	Service Check Save

en	Web Proxies

en	Web Proxie Edit

en	Save Web Proxy

en	CA

en	CA Edit

en	Save CA