suuhm/unblock-proxy.sh

domain and Subdomin

Closed this issue · 20 comments

Good time, thank you for this very good project

I need to proxy a domain and all its subdomains, how should I add it in the file or in the web panel?
Or how can all incoming requests be proxyed and there is no need to set the domain

suuhm commented

Hey yes its ez for the smartdns mode like just adding yourdomain.com in the web interface.

For transparent mode your need first enumerate all subdomains with tools like subfind3r oder dnscan or nmap

Like: python sublist3r.py -d yourdomain.com

Yes, I easily add the domains, but when I confirm the settings to be applied, it encounters an error, and after I add the domains once, it is completely disabled and gives this error every time.
dnsmasq[12610]: exiting on receipt of SIGTERM
I checked and explained that port 53 is being used, which is using
sudo kill -9 $ (sudo lsof -t -i:53)
I close the whole process, but when I run it with the command
unblock-proxy.sh dns --redsocks --web-admin
All the sites that I added to it do not load with the browser, but when
cmd
I get the domain nslookup and it returns correctly
I checked on several devices and it is the same problem

If it is possible, give me an email or a communication method, I need a service similar to yours for a project, and today I tested your service, it worked well, but after adding the domain, it stopped working.

Screenshot 2024-01-22 012553
this error
when not give any error
again not proxy dns requst
and show apache page in my server

suuhm commented

Do you get any issues and error when you put the domain in the domains.lst file?

You have maybe a buggy dnsmasq version so somerhing is killing the process here, need more log or strace infos here if possible.

Also you can try to disable dnsmasq at start with systemctl disable dnsmasq than reboot

Successful saved and restarted, now you can go back!

This message always appears when adding

Error when I added a domain
Jan 21 23:44:57 dnsmasq[1863]: exiting on receipt of SIGTERM

And I typed these two commands and executed the command again, it was activated correctly

systemctl disable sniproxy
systemctl disable dnsmasq
unblock-proxy.sh dns --redsocks --web-admin

Hello again, my problem was almost solved last night with the commands I sent, but now I have a problem again, so that sniproxy does not connect and port 443 does not open, how can I check this and fix it?

When it was correct, it stopped two sniproxy processes when it wanted to reset

suuhm commented

hmm seems to be a strange problem with your os or iptables maybe..
can you tell me which distribution you`re using?

you can also reset your tables first unblock-proxy.sh -R or better a fully restart of your os.
After that therse should nothing block the connect to the ports.

Also please check your /var/log/syslog and /var/log/messages or post it here if you have some issues

Tested on Ubuntu 20 and Ubuntu 22
Both have error can you fix this for me i need to add feature

Every time I try to activate the service, but this service is not activated and that's why it doesn't work

image

image

suuhm commented

Did you have the same problems with the domains.lst file or only by entering in webinterface?

It seems you have autostart on for dnsmasq . Can you please disable it with systemctl disbale dnsmasq && systemctl daemon-reload

and also give please output of: systemctl list-units --all

and Output of journalctl -xeu sniproxy

my domians.lst

## DOMAINS YOU WANT TO USE A PROXY
#
## ONE DOMAIN PER LINE!!

myip.is
ifconfig.co

output of: systemctl list-units --all

output.txt

output of: journalctl -xeu sniproxy

sni.txt

Disable auto start dnsmasq

suuhm commented

it looks like the problem is, that there is service blocking port 80 and port 443.

you can check with ss -tulpn | grep -E '80|443' which service is blocking

suuhm commented

you have to stop apache or disable the virtual host on port 80 to get your sniproxy work

Yes, the problem is that I install php with the command you posted above and it automatically creates itself on port 80, so how can I bring up the management panel on a port other than 80 and without the need to install apache

suuhm commented

just do this:

apt purge apache2 apache2-bin && apt install php-fpm php-cli

suuhm commented

If you got success please close the issue thanks

Yes, the problem is solved, thanks
I would like to add this project as a private feature if possible.

suuhm commented

All right , feel free to do 👍