System log - more details about shown errors

mwickel asked a question.

June 6, 2018 at 7:00 AM

Hi, Background: we run our Snow AP test environment on the intranet and make the website available via a TMG ForeFront for access via the Internet. This solution works wonderfully with the SLM. Since Snow AP has to communicate with other systems, there seem to be problems here and it's not possible to request any service. The request ends in an error message in the log "Server request failed". Now I would like to know more about this error in order to be able to make adjustments to the TMG or, if necessary, in the Snow AP. Where in the system can I find detailed information about this error? Unfortunately, I have not found any corresponding log files PS: Running Snow AP on the intranet all services working fine! Thanks and Best Mathias

Oskar Frolin (Flexera Software)
8 years ago
Hi Mathias, In my experience it is easier to go the "other way" and check where the error occurs. To do this, go to your browsers developer tools (usually F12) and then look at the requests (Network tab for Chrome dev tools), after you've gotten the error check the log for the faulty requests and continue from there, checking the content of the request and the response. Let me know if you find anything Example from Chrome: Question: One question on the issue is, are you using the same URL from the outside as from the inside? Hope this helps! BR Oskar
Expand Post
- mwickel
  8 years ago
  Hi Oskar, this helps a lot! Thanks you. We use a different URL internally than for external access. By your hint I found out that the call of the Snow AP API is forwarded from outside to an internal port, which is of course not reachable. https://external-url :8082 /API/RequestActivity/95/RequestParameter If I remove the port in the URL, you get the request information via the API interface https://external-url/API/RequestActivity/95/RequestParameter Now it's time to figure out how to stop this redirection. Because, this redirection happen on all API requests. Best, Mathias
  Expand Post
  - Portal User
    8 years ago
    Hi Mathias, The reason that it uses the internal address in the second call is that a self link is added as metadata of related objects to the DTO, that is later used for getting information. The self links are built automatically based on the address that AP is reached on. When browsing through TMG, AP will still see that the traffic comes in on the internal address. One way that might fix this is to modify the host header on all calls that are made from TMG to AP to have the external address as value. Best regards Tomas
    Expand Post