Pozdrav ekipa!
Molio bih za pomoc ako neko zna moguce razloge naseg problema.
Imamo u jednoj firmi windows 2012R2 server, to sve radi i funkcionise kako treba. Problem je nastao kada je azurirana aplikacija Maximizer (CRM aplikacija koju koriste) na novu verziju, sa 2017 je sve radilo ok, ali kada su iz podrske maximizera update-ovali na verziju 2019 nista nij radilo, pa smo donekle namestili i podesili da radi ali i dalje imamo problema...nije do njih nego treba njihov IT tim da resi problem, samo nemaju nikakve instrukcije da daju.
I sami Englezi kazu da nova verzija radi potpuno drugacije od stare, i da nam je server podesen kako treba, ali da nemaju ideju zasto neradi iz lokala, i da to mora da resi IT podrska njihova, odnosno mi. A i nenormalno su skupi za podrsku, a i sve sto su nam objasnjavali svodi se na jednu istu stvar samo na deset razlicitih nacina, da li hoce dodatnoda naplate, ali uvek ista poruka da treba njihov IT tim da resi.
Desava se sledeca stvar, posto je to web aplikacija, a oni hoce da im bude na lokalnom serveru, resili smo tako sto smo napravili poddomen na njihovom sajtu koji redirektuje saobracaj na lokal server. Sve to radi kada se pristupa spolja, odnosno van njihove lokalne mreze, takodje radi i sa mobilne aplikacije, ali isto tako Van lokalne mreze. Kada smo u njihovoj lokalnoj mrezi nece da radi, jednostavno kaze Secure Connection Faild, instalirani su SSL sertifikati i na webhostingu i na lokalnom serveru, iako dobijam na ssl testu rezultat koji cu staviti u prilog. A ono sto me buni, je i sto mi je logicnije da je sertifikat problem ne bi moglo ni spolja da se pristupi. Pristupamo spolja preko porta 11029, a kada postavim default port za secure 443 na mikrotiku onda radi iz lokala ali blokira internet saobracaj, radi tek poneki sajt, Youtube i jos nesto je radilo, i imamo uzvicnik na za mrezu kaze no internet.
Ne mogu nista da prilozim, ali evo sta kaze ssl testing tool:
Assessment failed: Failed to communicate with the secure server
Known Problems
There are some errors that we cannot fix properly in the current version. They will be addressed in the next generation version, which is currently being developed.
No secure protocols supported - if you get this message, but you know that the site supports SSL, wait until the cache expires on its own, then try again, making sure the hostname you enter uses the "www" prefix (e.g., "
www.ssllabs.com", not just "ssllabs.com").
no more data allowed for version 1 certificate - the certificate is invalid; it is declared as version 1, but uses extensions, which were introduced in version 3. Browsers might ignore this problem, but our parser is strict and refuses to proceed. We'll try to find a different parser to avoid this problem.
Failed to obtain certificate and Internal Error - errors of this type will often be reported for servers that use connection rate limits or block connections in response to unusual traffic. Problems of this type are very difficult to diagnose. If you have access to the server being tested, before reporting a problem to us, please check that there is no rate limiting or IDS in place.
NetScaler issues - some NetScaler versions appear to reject SSL handshakes that do not include certain suites or handshakes that use a few suites. If the test is failing and there is a NetScaler load balancer in place, that's most likely the reason.
Unexpected failure - our tests are designed to fail when unusual results are observed. This usually happens when there are multiple TLS servers behind the same IP address. In such cases we can't provide accurate results, which is why we fail.
Common Error Messages
Connect timed out - server did not respond to our connection request, sometimes before we are dynamically blocked when our tests are detected
No route to host - unable to reach the server
Unable to connect to server - failed to connect to the server, it usually happens due to firewall restrictions
Connection reset - we got disconnected from the server
Unrecognized SSL message, plaintext connection? - the server responded with plain-text HTTP on HTTPS port
Received fatal alert: handshake_failure - this is either a faulty SSL server or some other server listening on port 443; if the SSL version of the web site works in your browser, please report this issue to us
Failed to communicate with the secure server - No secure protocol supported. Possibly this server only supports a draft version of TLS 1.3
Svi predlozi i sugestije dobrodosli!
Hvala unapred!