Solved Host SinusBot inside Webspace

[SinusStudios]

Hello forum,

i'd like to know if it's possible to host the SinusBot admin panel inside my existing webspace,
let's say "domain.com/sinusbot/".

I've already asked my domain provider and he told me that because browser don't support SRV there is no way to have SinusBot run on another sub domain like sinusbot.domain.com when you're hosting a port 80 webspace on domain.com.

Ofcourse i could just link to the port on my website but i'd really like to implement it on port 80 if it's possible because we have people who are allowed to manage the bot but can't access web services outside of certain set ports (security reasons? firewall? i don't know) like port 80 in web browsers.

 

[irgendwr]

I've already asked my domain provider and he told me that because browser don't support SRV there is no way to have SinusBot run on another sub domain like sinusbot.domain.com when you're hosting a port 80 webspace on domain.com.

Your domain provider seems to be pretty stupid because this doesn't require SRV-Records. xD
If you have an own Webserver running you can try configuring a reverse proxy on a subdomain, we even have a guide on how to do this in our wiki

 

[SinusStudios]

Your domain provider seems to be pretty stupid because this doesn't require SRV-Records. xD
If you have an own Webserver running you can try configuring a reverse proxy on a subdomain, we even have a guide on how to do this in our wiki

I followed the guide precisely and set up a type A record for sb.domain.com to my VS' IP. Then i configured a no-ssl configuration file and saved it in /etc/apache2/sites-available/sinusbot.conf
Then i executed this ln -sf /etc/apache2/sites-available/sinusbot.conf /etc/apache2/sites-enabled and restarted apache. Then i edited the config of SinusBot according to the bottom link and restarted the entire VS (apache and SinusBot auto-boot, checked.)
There are no error logs in either log outputs but sb.domain.com simply shows the VS' webspace and no given port shows SinusBot. Also not the old one (vs.domain.com:8087).
Any ideas?

 

[irgendwr]

This is probably due to misconfiguration of the new apache virtual host.
Can you send us your sinusbot.conf?

 

[SinusStudios]

This is probably due to misconfiguration of the new apache virtual host.
Can you send us your sinusbot.conf?

<VirtualHost *:80>
    ServerName sb.gnyb.de

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    ProxyPreserveHost On

    ProxyPass / http://127.0.0.1:8087/
    ProxyPassReverse / http://127.0.0.1:8087/

</VirtualHost>

 

[irgendwr]

<VirtualHost *:80>
    ServerName sb.gnyb.de

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    ProxyPreserveHost On

    ProxyPass / http://127.0.0.1:8087/
    ProxyPassReverse / http://127.0.0.1:8087/

</VirtualHost>

Try remaming the config and the link to 0a-sinusbot.conf
(Apache is stupid)
If this still doesn't work show us the output oft ls -la in the config folder

 

[SinusStudios]

Try remaming the config and the link to 0a-sinusbot.conf
(Apache is stupid)
If this still doesn't work show us the output oft ls -la in the config folder

It worked! Witchcraft!
Thanks a lot for the help =)
Regards, Daniel

 

[irgendwr]

It worked! Witchcraft!
Thanks a lot for the help =)
Regards, Daniel

No Problem, as I said: Apache is stupid