This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
1
CentOS 7 Problems / Re: Cant use my hostname address to connect to smtp
« on: October 19, 2022, 09:04:53 AM »
what is weird is that if I create an SSL within the client side it works fine as I said in my main post. I don't really care so long I am getting an SSL I am good what I am afraid of is that this will start on everything that in involved with SSL emails
2
CentOS 7 Problems / Re: Cant use my hostname address to connect to smtp
« on: October 18, 2022, 07:15:26 AM »
CWPpro version: 0.9.8.1146
ionos vps
ionos vps
3
CentOS 7 Problems / Cant use my hostname address to connect to smtp
« on: October 18, 2022, 07:00:02 AM »
This problem is rising reasonably quickly now when I set their emails with SSL using my hostname and they are getting errors. I always did this way for years and something I am a bit worried about. But if I set up SSL with mail.theirDomain.com then it works that is what I am currently doing now at this moment. this is the error that my clients are receiving.
Task 'info@theirDomain.com - Sending' reported error (0x800CCC1A) : 'Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or Internet service provider (ISP) for additional assistance.'
Thank you
Task 'info@theirDomain.com - Sending' reported error (0x800CCC1A) : 'Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or Internet service provider (ISP) for additional assistance.'
Thank you
4
CentOS-WebPanel Bugs / Re: Auto Log out after login in Dashboard
« on: August 23, 2020, 04:16:44 PM »
My apologies it was my IP changing. I thought google what is my IP updates live but it does not so it's my service provider that changes IP all the time really sorry.
5
CentOS-WebPanel Bugs / Re: Auto Log out after login in Dashboard
« on: August 23, 2020, 03:37:45 PM »
Is there an access log that anyone knows I can check to see what is the problem?
I been on this for hours now and can't see what is the problem. I never had this problem and I have been using this for years now
I been on this for hours now and can't see what is the problem. I never had this problem and I have been using this for years now
6
CentOS-WebPanel Bugs / Re: Auto Log out after login in Dashboard
« on: August 23, 2020, 02:57:15 PM »
But IP is not changing. I checked it my public IP is always the same.
And when I login most of the time it instantly logged out after it logs in. I will have the dashboard but within the dashboard, it is asking me to log in its weird
And when I login most of the time it instantly logged out after it logs in. I will have the dashboard but within the dashboard, it is asking me to log in its weird
7
CentOS-WebPanel Bugs / Auto Log out after login in Dashboard
« on: August 19, 2020, 01:01:48 PM »
I will login my CWP I do get to the dashboard but when you select something or refresh it logs out back into the Login screen. Sometimes It will let me do some stuff but most of the time its right at the dashboard and it logs out
8
CentOS 7 Problems / nginx fails
« on: March 10, 2018, 06:20:35 PM »
Good day everybody
I am just having a issue when I apache setting and then on Select WebServer when I select nginx
I get this error:
Nginx ERROR Detected ! nginx: [emerg] invalid port in upstream "123.123.123.123:PROXYPORT" in /etc/nginx/conf.d/server1.domain.com_ssl.conf:31 nginx: configuration file /etc/nginx/nginx.conf test failed
I googled for a bit and cant really see what the problem is
Here is my /etc/nginx/conf.d/server1.domain.com_ssl.conf file
I am just having a issue when I apache setting and then on Select WebServer when I select nginx
I get this error:
Nginx ERROR Detected ! nginx: [emerg] invalid port in upstream "123.123.123.123:PROXYPORT" in /etc/nginx/conf.d/server1.domain.com_ssl.conf:31 nginx: configuration file /etc/nginx/nginx.conf test failed
I googled for a bit and cant really see what the problem is
Here is my /etc/nginx/conf.d/server1.domain.com_ssl.conf file
Code: [Select]
# Virtual host file starts here
server {
listen 123.123.123.123:443;
access_log /var/log/nginx/access.domain.com.log;
error_log /var/log/nginx/error.domain.com.log;
server_name domain.com www.domain.com;
root /home/domain/public_html;
ssl on;
ssl_certificate /etc/pki/tls/certs/domain.com.bundle;
ssl_certificate_key /etc/pki/tls/private/domain.com.key;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS;
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:20m;
ssl_session_timeout 60m;
add_header Strict-Transport-Security "max-age=31536000";
add_header X-Content-Type-Options nosniff;
location / {
location ~.*\.(3gp|gif|jpg|jpeg|png|ico|wmv|avi|asf|asx|mpg|mpeg|mp4|pls|mp3|mid|wav|swf|flv|html|htm|txt|js|css|exe|zip|tar|rar|gz|tgz|bz2|uha|7z|doc|docx|xls|xlsx|pdf|iso|woff|ttf|svg|eot|sh)\$ {
expires 7d; #Comment this out if you are using the apache backend cache-control/expires headers.
try_files \$uri \@backend;
}
error_page 405 = \@backend;
error_page 500 = \@custom;
add_header X-Cache "HIT from Backend";
proxy_pass http://123.123.123.123:82;
include proxy.inc;
}
location \@backend {
internal;
proxy_pass http://123.123.123.123:82;
include proxy.inc;
}
location \@custom {
internal;
proxy_pass http://123.123.123.123:82;
include proxy.inc;
}
location ~ .*\.(php|jsp|cgi|pl|py)?\$ {
proxy_pass http://123.123.123.123:82;
include proxy.inc;
}
location ~ /\.ht {
deny all;
}
}
# Virtual host file ends here
and /etc/nginx/nginx.conf fileCode: [Select]
# Nginx config starts here
user nobody;
worker_processes auto;
#worker_rlimit_nofile 20480;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 4096; # increase for busier servers
use epoll; # you should use epoll for Linux kernels 2.6.x
multi_accept on;
}
http {
open_file_cache max=5000 inactive=30s;
open_file_cache_valid 120s;
open_file_cache_min_uses 2;
open_file_cache_errors off;
open_log_file_cache max=1024 inactive=30s min_uses=2;
server_names_hash_max_size 10240;
server_names_hash_bucket_size 1024;
include mime.types;
default_type application/octet-stream;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 20;
gzip on;
gzip_vary on;
gzip_disable "MSIE [1-6]\.";
gzip_proxied any;
gzip_http_version 1.1;
gzip_min_length 1000;
gzip_comp_level 6;
gzip_buffers 16 8k;
gzip_types text/plain text/xml text/css application/x-javascript application/xml image/png image/x-icon image/gif image/jpeg application/xml+rss text/javascript application/atom+xml application/javascript application/json;
ignore_invalid_headers on;
client_header_timeout 3m;
client_body_timeout 3m;
client_max_body_size 200m;
send_timeout 3m;
connection_pool_size 256;
client_header_buffer_size 4k;
large_client_header_buffers 4 32k;
request_pool_size 4k;
output_buffers 4 32k;
postpone_output 1460;
proxy_temp_path /tmp/nginx_temp;
log_format bytes_log "$msec $bytes_sent .";
# Include site configurations
include /etc/nginx/conf.d/*.conf;
}
9
CentOS 7 Problems / Re: Hostname changes on every reboot
« on: February 27, 2018, 03:47:16 PM »
I did some research on this problem and I have sort it out by locking the hostname file and I just did hosts aswell just incase I think its the hosting provider that did this but here i used this code.
To lock
To unlock
If there is a problem with this to cwp please some one let me know thank you
To lock
Code: [Select]
chattr +i /etc/hosts /etc/hostname
To unlock
Code: [Select]
chattr -i /etc/hosts /etc/hostname
If there is a problem with this to cwp please some one let me know thank you
10
CentOS 7 Problems / Re: Hostname changes on every reboot
« on: February 23, 2018, 12:53:57 PM »
I am thinking I am getting confused between fqdn and hostnames but still not sure how to sort it out
11
CentOS 7 Problems / Re: Hostname changes on every reboot
« on: February 23, 2018, 12:07:55 PM »
Just want to add one thing its not the vps settings that is set to "server1.domain.com"
12
CentOS 7 Problems / Re: Hostname changes on every reboot
« on: February 23, 2018, 12:02:52 PM »
/etc/hosts
This does not change until I update the hostname from the web interface
This does change when I update or restart
that is what I change it to
This does not change until I update the hostname from the web interface
Code: [Select]
127.0.0.1 localhost.localdomain localhost
# Auto-generated hostname. Please do not remove this comment.
123.123.123.123 server1.domain.com server1
::1 localhost
/etc/hostnameThis does change when I update or restart
that is what I change it to
Code: [Select]
server1.domain.com
after rebootCode: [Select]
server1
13
CentOS 7 Problems / Re: Hostname changes on every reboot
« on: February 23, 2018, 11:35:56 AM »
Ok I sorted out the http test I accidentally changed the shared IP
But still sorting out host name
But still sorting out host name
14
CentOS 7 Problems / Re: Hostname changes on every reboot
« on: February 23, 2018, 11:28:12 AM »
for some reason now all my pages are "HTTP Test Page" so everything is kinda broken and dont know what to do about it
15
CentOS 7 Problems / Re: Hostname changes on every reboot
« on: February 23, 2018, 10:48:42 AM »
Million things popped up dont know what to do with it really sorry
Pages: [1] 2