I can not access the admin page

Before.
‘’’
server.ssl.cert=./server.crt
server.ssl.key=./server.pem
server.ssl.key.pass=xxxxxx

#server.host=.

#contact.email=.

Now.

server.ssl.cert=
server.ssl.key=.
server.ssl.key.pass=
‘’’
server.host=.

contact.email=.

  • Didn’t find custom user certificates.
  • Didn’t find Let’s Encrypt certificates.
  • Automatic certificate generation is turned ON.
  • WARN - ATTENTION. Server certificate paths (cert : ‘C:\BlynkServer’, key : ‘C:\BlynkServer’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.
  • Hardware plain tcp/ip server listening at 8442 port.

Your console shows error. Are your host available via 80 port?

Make sure that last little period is NOT actually in your server.properties file

I can not open port 80, error.

IP 192.168.xxx.xxxxThis text will be hidden = Server.

@Gunner
server.ssl.key= .
It was only time to copy and paste.

80 port is opened by default on all router. But Blynk server runs HTTP on port 8080 (security measure). Certificates request comes to port 80 (security measure, that proves you are the owner of host). So you have to forward request from port 80 to port 8080.

Look at this post

@Dmitriy Is correct 8080 to 80?

Like this:

server.host=mc-casainteligente.ddns.net

contact.email=mauroviana.s@hotmail.com

I have this error.
Logs:

  • Didn’t find custom user certificates.
  • Didn’t find Let’s Encrypt certificates.
  • Automatic certificate generation is turned ON.

@Fettkeewl, Did not work 0.0.0.0/0

Edit: Does that explain anything?

@mauroviana seems correct.

Regarding error:

I guess that you should wait a hour... From https://letsencrypt.org/docs/rate-limits/660: 
1 Like

Your internal ports should match that of your server.properties file.
Port 80 from external access goes to 8080 on internal access
Port 443 from external access to 9443 on internal.

Change in your first column in router settings. And you need my previous answer as well else you can’t login from outside your LAN

1 Like

As this issue was growing in size, I moved it to it’s own topic so as not to crowd the announcement topic (any more :wink: ).

1 Like

Is correct?

I get it.

OK sorry.
Port: 443 ok.

Port: 80 to 8080.

My router does not let me redirect the port 80 to 8080. I don’t know do this. Can help me?

@Fettkeewl Now I have:

Logs:

  • Didn’t find Let’s Encrypt certificates.

  • Automatic certificate generation is turned ON.

  • WARN - ATTENTION. Server certificate paths (cert : ‘C:\BlynkServer’, key : ‘C:\BlynkServer’) not valid. Using embedded server certs and one way ssl. This is not secure. Please replace it with your own certs.

  • Starting up certificate retrieval process for host mc-casainteligente.ddns.net and email mauroviana.s@hotmail.com.

  • mauroviana.s@hotmail.com hardware joined.

  • Registered a new user, URI: https:/acme-v01.api.letsencrypt…

  • Authorization for domain mc-casainteligente.ddns.net

  • Delivering content XPHlDwj6hPZoDSB1sic5vrvDn…

  • Found server certificate but no client certificate for ‘C:\BlynkServer\non-existing-client.crt’ path. Using one way ssl.

But I still can not open the admin page with seconds.

Now that you have proper settings assuming you added allowed IPs to be that 0.0…range
You must use your domain name to connect
With https specified. Not internal IP.

I.e
https://yourdomain/admin
It will automatically try to connect over port 443 for the https connection and will be redirected by your router to your computer on your computers port 9443. Make sure your pc firewall is not actively blocking your ports.

1 Like

I admit that I have the same “Not Secure” error, but I just bypass it since it doesn’t really matter to me. I have generated certs from last year when I first installed Local Server, but I never access it outside my LAN anyhow. So how would one enter a domain name from within a local network? I mean… what domain name? I just have a Local Server IP - https://10.10.3.13:9443/admin - all locked off from my WAN side.

I don’t think you can unless you have some software installed that can solve it, don’t know of any. :neutral_face:
I use noip.com as my dns service, I connect to them when I enter my domain and they basically reroute me back to my network and then to my pc which has the blynk server running.

Using lets encrypt, needs a domain name to function apparently that is why it’s in discussion, unless you use it there is no need to fiddle with domain names, if you don’t need WAN access :slight_smile:

Thank you all, now it seems all right.

@Fettkeewl I was only able to open port 80 for Blynk by making this setting on the router.
You can tell me if that’s right, before it was like this.

Now it’s like this.

Do you have any opinion on safety

Sorry I don’t understand what is written on your pictures…

It’s ok.
I’ll research about security and remote management of the router.
Now it looks like it’s going well.:smile:
But username and password admin seems to be in trouble. Because I changed the password in the file “server.properties” file and nothing change in the login screen. I reloaded the server and nothing changed. I can only sign in with the previous user and password.

@mauroviana changing the username and password is not very straightforward.

I’m informed the procedure is stop the server, delete the user that had the original password and then when you start the server the entries in server.properties should work. Don’t try messing with the json details if the user i.e isSuperAdmin:true as that makes matters worse.

When you start the server via a console it will tell you the allocated username and password (for the first time) after deleting the general admin user.