xtream v1 enable SSL and HTTPS redirect

[sambir]

Anyone managed to enable this on a non standard port and on v1 cracked panel? Could be a nice feature ofcourse and make the connections more secure especially these periods... Please share your thoughts if its even possible or not...

 

[kskturk]

I think you can do it, brother

ftp connect go to xtream codes crack panel

/home/xtreamcodes/iptv_xtream_codes/nginx/conf open

code paste :

sample my conf: listen 8080; listen 80; listen 443; and server reboot

but the ssl extension xxx.com has to have ssl license

and customers can connect to ssl from port 443.

good shares ...

 

[sambir]

I think you can do it, brother

ftp connect go to xtream codes crack panel

/home/xtreamcodes/iptv_xtream_codes/nginx/conf open

code paste :

sample my conf: listen 8080; listen 80; listen 443; and server reboot

but the ssl extension xxx.com has to have ssl license

and customers can connect to ssl from port 443.

good shares ...

Could you send a sample file? How about users tryping to download their m3u file? All initial connections must be redirected to the ssl connection.

Lets say they connect with default port 8000 this must be redirected to the secure 443 ssl port. I think permanent redirect. But dont know if streaming over 441 is a good idea... I was wondering if for instance streaming over 8000 and ssl is possible...

 

[kskturk]

need to try

but i think it works

i don't use ssl
but the action needs to be done from the nginx folder ngnix.conf

 

[sambir]

need to try

but i think it works

great! but I am wondering if clients will be able to cope with the secure connection like enigma2 devices and smart tv's maybe thats the reason it was never implemented... Still would be nice if the management panel could be secured at least. V2 the management cms was secure also. streams where not I think.

 

[noshi421]

I think you can do it, brother

ftp connect go to xtream codes crack panel

/home/xtreamcodes/iptv_xtream_codes/nginx/conf open

code paste :

sample my conf: listen 8080; listen 80; listen 443; and server reboot

but the ssl extension xxx.com has to have ssl license

and customers can connect to ssl from port 443.

good shares ...

cheers mate... thanks