pixelserv pixelserv - A Better One-pixel Webserver for Adblock

[M@rco]

Actually I just saw the wiki going to run that now.

Make sure you choose the correct option (LAN/VPN, WAN)

Use your Pixelserv CA to issue a certificate to domain:

  a. router.asus.com
  b. wouldntyouliketoknow.ddns.net

Note that (a) works from LAN and VPN. It's recommended.
(b) additionally works for access from WAN.

 

[kvic]

Make sure you choose the correct option (LAN/VPN or WAN)

Great to hear. I recall I did mention a few conditions that the script need to be re-run. However, I can't find it myself on the Wiki. Must be littered somewhere in one of the replies.

I suspect NVRAM or /jffs is erased in this FW upgrade. One of these conditions will require re-run the script.

When you get a better picture of the conditions, pls let me know and I could update the Wiki. Or I believe you could update it as well.

 

[M@rco]

Great to hear. I recall I did mention a few conditions that the script need to be re-run. However, I can't find it myself on the Wiki. Must be littered somewhere in one of the replies.

I suspect NVRAM or /jffs is erased in this FW upgrade. One of these conditions will require re-run the script.

Here are the conditions you mentioned: https://github.com/kvic-z/pixelserv...ssue-a-certificate-for-WebGUI#config-webguish

I'm fairly certain neither NVRAM or /jffs were erased during the firmware upgrade. All scripts were there when rebooting, VPN server and client came online, my pool of static dhcp leases was intact. All of this would have been erased too, right?

 

[Asad Ali]

Did you upgrade to 384.7 beta?

 

[M@rco]

Did you upgrade to 384.7 beta?

Me? Yes.

 

[Asad Ali]

Me? Yes.

Since 384.7 have some major changes to DDNS code , its possible that it messed up with your imported certificate during the upgrade process.

 

[kvic]

Here are the conditions you mentioned: https://github.com/kvic-z/pixelserv-tls/wiki/[ASUSWRT]-Use-Pixelserv-CA-to-issue-a-certificate-for-WebGUI#config-webguish

I'm fairly certain neither NVRAM or /jffs were erased during the firmware upgrade. All scripts were there when rebooting, VPN server and client came online, my pool of static dhcp leases was intact. All of this would have been erased too, right?

If the scripts are still there, /jffs as a partition then seems intact. I suspect this FW upgrade has overwritten one or more of the following:

• nvram variable: https_crt_file
• /jffs/ssl
• /jffs/ssl/cert.pem
• /jffs/ssl/key.pem

 

[kvic]

Since 384.7 have some major changes to DDNS code , its possible that it messed up with your imported certificate during the upgrade process.

@Makaveli does have a weird cert issued to XXX.ddns.net...

 

[Asad Ali]

@Makaveli does have a weird cert issued to XXX.ddns.net...

And it's possible that the weird cert become even more weirdest during the upgrade and broke lol [emoji1787][emoji1787]

 

[M@rco]

@Makaveli does have a weird cert issued to XXX.ddns.net...

Isn't that just the result of choosing option b in config-webui.sh? Never tried it, but reading the wiki made me think so...

 

[kvic]

Isn't that just the result of choosing option b in config-webui.sh? Never tried it, but reading the wiki made me think so...

I would think so too.
But Makaveli's situation is a bit weird. E.g the expiry date is Aug 12, 2018. That's impossible if generated by the script.
Good that he has it all sorted out. lol

 

[Makaveli]

Isn't that just the result of choosing option b in config-webui.sh? Never tried it, but reading the wiki made me think so...

On my end there seems to be something weird when I use Let's Encrypt vs Import/Persistent Auto generated. So going to continue checking this.

This looks good now.

 

[M@rco]

Since 384.7 have some major changes to DDNS code , its possible that it messed up with your imported certificate during the upgrade process.

That makes sense. Allthough I haven't seen it on alpha 1 and 2 (I skipped 3), so maybe it has something to do with changes made prior to release beta 1. Well, luckily it can be fixed easily be re-running config-webui.sh. @kvic, you might consider rephrasing the condition

Note that re-run only required if you perform factory resets.

in the wiki. From what I understand, re-running it doesn't do any harm either, so it might help more people fix their own issues, instead of posting to this thread, complaining about broken padlocks and blabla, like... me

 

[Asad Ali]

I would think so too.
But Makaveli's situation is a bit weird. E.g the expiry date is Aug 12, 2018. That's impossible if generated by the script.
Good that he has it all sorted out. lol

Probably when he generated the certificate, router time was not up-to-date.

Just a guess..... [emoji848][emoji848]

 

[kvic]

you might consider rephrasing the condition

So... the condition was indeed mentioned in the Wiki. Updated now!

 

[kvic]

Probably when he generated the certificate, router time was not up-to-date.

Just a guess..... [emoji848][emoji848]

Let's fancy she was simply drunk

 

[Asad Ali]

Let's fancy she was simply drunk

Ok Deal. [emoji1635]

 

[Makaveli]

Ok Deal. [emoji1635]

lol he i'm a guy and i've updated post 2294 good to go now.

 

[Asad Ali]

lol he i'm a guy and i've updated post 2294 good to go now.

Ok Deal cancel then. [emoji16][emoji16][emoji1787]

 

[elorimer]

If the scripts are still there, /jffs as a partition then seems intact.

Not entirely sure about that. It is possible /jffs got resized and parts of some files left out of bounds, yes? So restoring from backup maybe a good idea.