• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Verifying Reverse Proxy is working documentation within the PowerServer environment. Something seems to be missing

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Verifying Reverse Proxy is working documentation within the PowerServer environment. Something seems to be missing

  1. How-to
0
Votes
Undo
  1. Esau Redwan
    Esau Redwan
  2. PowerServer
  3. Friday, 2 February 2024 00:22 AM UTC

Hello All,

 

I am setting up the reverse proxy in NGINX and I am ready to test if it works.

I referenced this documentation here in the R3 version: https://docs.appeon.com/ps2022r3/Verifying_the_configuration_for_Nginx_Windows.html

In that documentation, it mentions to change the apprun.json to point to my reverse proxy server and run the project in SnapDevelop which I did.

Running in SnapDevelop brings up the cmd line window but it doesnt show nearly as much logs as the documentation shows. I do not see where the APIs are resolving to. (im looking to see that its going to the reverse proxy server first) It just looks like the normal cmd line window that runs in a local PowerServer deployment. 

 

Do I need to enable more logging or something else that was not mentioned in the documentation? 

 

Thank You!

PBAutoBuild - Menu icons were missing in PowerServ...
Powerserver build overwriting ini files after each...
Accepted Answer
Esau Redwan
Esau Redwan Accepted Answer Pending Moderation
  1. Friday, 2 February 2024 22:19 PM UTC
  2. PowerServer
  3. # Permalink
I found it. The logging config to change is in Logging.json not Logging.Development.json. Once I changed the entries in Logging.json, I was able to see the API requests.
Comment
Tracy Huang @Appeon
  1. Tracy Huang @Appeon
  2. Sunday, 4 February 2024 01:06 AM UTC
Thank you for the verification. You reminded me that Logging.json is used in the production environment and Logging.Development.json is used in the development environment. I will add this (and the updated path) to documentation.
  1. Helpful 1
There are no comments made yet.
Responses (2)
Tracy Huang @Appeon
Tracy Huang @Appeon Accepted Answer Pending Moderation
  1. Friday, 2 February 2024 06:13 AM UTC
  2. PowerServer
  3. # 1

Hi Esau,

Please set the PowerServer log level to "Debug" to view more logs in the server console. The default log level is changed from "Debug" to "Warning" in version 2022. 

For detailed instructions, refer to https://docs.appeon.com/ps2022r3/PowerServer_log_level_changes.html.

Regards

Tracy

Comment
Load more comments
Esau Redwan
  1. Esau Redwan
  2. Friday, 2 February 2024 21:06 PM UTC
Thank you for the update. By the way I didn't see it in " ServerAPIs project > Logging >". It was located in Solution->UserExtensions->Logging->Loggin.json-> LoggingDevelopment.json
  1. Helpful
Esau Redwan
  1. Esau Redwan
  2. Friday, 2 February 2024 21:34 PM UTC
I was able to change the logging to debug but its still not showing the request to the API address that I modified in apprun.json so I cannot verify if its reaching the Nginx reverse proxy server or not. Do you know why this might be happening?
  1. Helpful
Esau Redwan
  1. Esau Redwan
  2. Friday, 2 February 2024 21:40 PM UTC
The log screenshot in the Appeon documentation says the log level is info not debug: https://docs.appeon.com/ps2022r3/images/kestrel_9.png



Is there something else I need to do to show the requests to the API?
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.