Node JS - setting up security provider

[crystaltaggart]

I’m trying to follow this post to set up a secure page.

• I’ve added my secure provider to my API.
• I’ve added my server connect action to my template.

I can see the login page rendered in the response, but the screen doesn’t update.
Is there something else that I need to do to render the login page or redirect?

[scott]

What server type are you using? PHP, Nodejs, or something else?

I can see the file is an html file, but I am not sure about what type of server.

Edit: Nevermind, I see you tagged nodejs in the post title.

This may be related to a bug that has been previously reported and should have a fix in the next update.

Cannot set headers after they are sent to the client

Wappler Version : 3.5.4 Operating System : Catalina Server Model: NodeJS Database Type: PG Hosting Type: Local Actual behavior What actually happens? [image] How to reproduce I’ve seen it happen in several parts of the app but the easiest way to reproduce is: Restrict a page and redirect elsewhere if not logged/authorized

However, in case it is not, please take a screenshot of your server connect action, showing what you have put in for the Security Restrict.

[crystaltaggart]

Here’s my Security Restrict:

[scott]

While there is a known issue involving using the Routes picker in the Security Restrict,

Route picker URL not working on Security Restrict

Wappler Version : 3.5.5 Operating System : MacOS Catalina Server Model: Nodejs Database Type: PG Hosting Type: Local Expected behavior What do you think should happen? Picking a route in Security Restrict from the route selector for a path should add it Actual behavior What actually happens? Nothing How to reproduce Select a Security Restrict action Try to add a login URL or Forbidden URL via Route selection

I am confused by the routes you selected. Did you manually type them in or did you use the route picker icon? The reason I ask is the /.../ stands out to me as a problem.

[crystaltaggart]

Actually I just looked at Jon’s post. I think it’s the same issue - seeing the same error in the local web server console.

[crystaltaggart]

I used the route picker. I try not to hand type anything if I can avoid it.

[scott]

@crystaltaggart

Actually I just looked at Jon’s post. I think it’s the same issue - seeing the same error in the local web server console.

Ok, try the solution in that topic thread and see if that corrects the issue.

@crystaltaggart

I used the route picker. I try not to hand type anything if I can avoid it.

I'm the same way, Wappler has spoiled me to where I don't like doing anything in code anymore.