pixelserv pixelserv - A Better One-pixel Webserver for Adblock

[snixel]

Ok, thanks alot for your help!

 

[DonnyJohnny]

I have a question. I noticed that pixelserv-tls listen to 443 (default) and 2443 if specified. I would like to use port 443 tcp for my openvpn. Can I make pixelserv-tls to listen to 2443 using the -k switch and will it still work? Other than the -k switch, do I still need to do anything like modifying the iptables or anything?

Thanks in advance

 

[elorimer]

I have a question. I noticed that pixelserv-tls listen to 443 (default) and 2443 if specified. I would like to use port 443 tcp for my openvpn. Can I make pixelserv-tls to listen to 2443 using the -k switch and will it still work? Other than the -k switch, do I still need to do anything like modifying the iptables or anything?

Thanks in advance

In the custom config box for your openvpn server, put "local <whatever your ddns address is>" That will cause openvpn to only listen on the wan side, not the lan side. Leave pixelserv on 443 and it will be listening on the lan side.

 

[DonnyJohnny]

Wow.. that’s easy and it is working.. thanks.

 

[rromeroa]

In the custom config box for your openvpn server, put "local <whatever your ddns address is>" That will cause openvpn to only listen on the wan side, not the lan side. Leave pixelserv on 443 and it will be listening on the lan side.

Wow, really works without iptables configuration...
But, openvpn servr doesnt start at boot, it must be started manually because at start time is not able to resolve ddns address, maybe a delay is necessary?

 

[DonnyJohnny]

Wow, really works without iptables configuration...
But, openvpn servr doesnt start at boot, it must be started manually because at start time is not able to resolve ddns address, maybe a delay is necessary?

Hi,

I also have the same experience. From what I read from the syslog,

Dec 27 02:48:30 openvpn[1336]: TCP/UDP: Socket bind failed on local address [AF_INET]123.123.123.123:443: Cannot assign requested address
Dec 27 02:48:30 openvpn[1336]: Exiting due to fatal error

The 123.123.123.123 is the previous IP address and not the current IP address after reboot. Ddns update only initialised after openVPN service started.

Not sure how to move it up the ddns update. Please advise. Thanks.

 

[elorimer]

My IP address changes rarely, so I haven't seen this, but ddns_update runs after the vpnserver starts.

You might try creating a ddns-start script (that runs after the ddns update returns the address) that has the line service restart_vpnserver1. I think that might work.

Also, it is worth having the second vpn server on 1194. If nothing else you can vpn into it, and restart the other.

 

[rromeroa]

My IP address changes rarely, so I haven't seen this, but ddns_update runs after the vpnserver starts.

You might try creating a ddns-start script (that runs after the ddns update returns the address) that has the line service restart_vpnserver1. I think that might work.

Also, it is worth having the second vpn server on 1194. If nothing else you can vpn into it, and restart the other.

Thanks @elorimer

I have tested the ddns-start script, it seems that it works but it has been necessary a "sleep 20" before restart vpnserver.

 

[jrmwvu04]

Any word on when the new version will hit the entware-ng repo?

 

[thelonelycoder]

Any word on when the new version will hit the entware-ng repo?

While @ryzhov_al and @zyxmon are regularly updating the repo as seen here: https://github.com/Entware-ng/Entware-ng/commits/master
, pixelserv is still awaiting its turn: https://github.com/Entware-ng/Entware-ng/issues/814

 

[ryzhov_al]

Any word on when the new version will hit the entware-ng repo?

Done! Binaries will arrive soon.

 

[DonnyJohnny]

Updated to 2.01. Nice...

 

[Protik]

If the stable is available from the entware, I would like to know what would be the safest way to revert back to the stable version. Any help regarding this will be appreciated.

Anyway, just to tinker, I tried opkg update && opkg upgrade and got the following error for lighttpd.

Collected errors:
 * resolve_conffiles: Existing conffile /opt/etc/lighttpd/lighttpd.conf is different from the conffile in the new package. The new conffile will be placed at /opt/etc/lighttpd/lighttpd.conf-opkg.

lighttpd is tied to pixelserv-tls and that error broke pixelserv-tls. I used Ab-Solution to disable and reinstall pixelserv-tls and everything was fine again.

 

[DonnyJohnny]

I too used ab-solution to reset setting and reinstall

 

[thelonelycoder]

If the stable is available from the entware, I would like to know what would be the safest way to revert back to the stable version. Any help regarding this will be appreciated.

Anyway, just to tinker, I tried opkg update && opkg upgrade and got the following error for lighttpd.

Collected errors:
 * resolve_conffiles: Existing conffile /opt/etc/lighttpd/lighttpd.conf is different from the conffile in the new package. The new conffile will be placed at /opt/etc/lighttpd/lighttpd.conf-opkg.

lighttpd is tied to pixelserv-tls and that error broke pixelserv-tls. I used Ab-Solution to disable and reinstall pixelserv-tls and everything was fine again.

I too used ab-solution to reset setting and reinstall

I'm seeing a strange behavior with the Entware package update for pixelserv-tls which was released yesterday as pixelserv-tls 2.0.1-1.
I have posted an issue over at GitHub, we'll see what comes of it:
https://github.com/Entware-ng/Entware-ng/issues/850

Until this is resolved hold back on updating pixelserv-tls through AB-Solution.

 

[M@rco]

Is pixelserv v35.HZ12.Kk the current version?

Edit: nevermind, the issue posted by the @thelonelycoder on Github cleared things up.

 

[Protik]

I'm seeing a strange behavior with the Entware package update for pixelserv-tls which was released yesterday as pixelserv-tls 2.0.1-1.
I have posted an issue over at GitHub, we'll see what comes of it:
https://github.com/Entware-ng/Entware-ng/issues/850

Until this is resolved hold back on updating pixelserv-tls through AB-Solution.

I see. I can't help about new installs. Whenever there is something new, I am like.. don't do it... don't do it... don't do it... did it and broke it...

 

[M@rco]

Until this is resolved hold back on updating pixelserv-tls through AB-Solution.

Ooops... guess I was too quick. And that @ 7:50 AM

 

[thelonelycoder]

Ooops... guess I was too quick. And that @ 7:50 AM

Don't get me wrong: There is nothing wrong with the released pixelserv-tls 2.0.1-1. It's just that the listed packages in opkg lists both the old and new version and it will not update if you run it through AB. Even a manual update with opgk update && opkg upgrade will not do it.
Hence my issue posted at the Entware-ng GitHub.

 

[Correlor]

@thelonelycoder

I had the same problem only 'opkg remove pixelserv-tls' did not work for me.
But deleting all lines in the file 'status' under directory '/mnt/sda1/enware-ng/lib/opkg' (in my setup) concerning pixelserv-tls did the trick.