Koning
asked on
Firewalld, Need help on allowing a third party IP thur my firewall to allow content to be add to my domain on my server
How do i allow a third party IP Address or domain.com to come thru my firewallD for Centos 7. I need a step by step explanation how to do this. This is the situation, I have a site builder module installed on my control panel. When i access it, it takes me to the third party company where i do the site creation. Once the site is completed, i have to publish it to a domain on my server. The only way to do this is allow the third parties ip address access so i can publish the content to a domain on my system. Please Help
Please give firewall detail or are you using by default firewall
You've asked many questions with the barest of configuration detail, so my answers will only be surface.
1) How do i allow a third party IP Address or domain.com to come thru my firewallD for Centos 7.
This depends on what type of access your trying to grant.
In the case of ssh, you'll have to create a key for them + send them the key + add an iptables rule to allow their IP to access your site or machine.
SFTP will just be an iptables rule.
If you're running a CMS like WordPress, then you'll just add a user with the appropriate role level... so if they're only suppose to be adding content, then their role will be contributor or editor. This depends on WordPress version you're running + how you manage your roles.
Generally this will work...
Be sure to use -I (insert) to place this rule at top of all rules, so it takes precedence.
If you use -A (add) there's a good chance other firewall rules will block the IP before your rule fires.
Also for complex firewall setups, the above will be insufficient. For some firewall setups, you'll require going through all your CHAINS + adding an exception in the correct chain.
2) I need a step by step explanation how to do this.
Same answer as #1. Depend on type of access they require.
Also, if you're running WHM or CPanel steps will be complex. Best hire someone.
Note: WHM + CPanel tend to create complex chains, which will require review to determine correct place to insert your rule or get into your WHM + CPanel docs to determine how to do this or open a support ticket with your hosting company.
3) This is the situation, I have a site builder module installed on my control panel. When i access it, it takes me to the third party company where i do the site creation. Once the site is completed, i have to publish it to a domain on my server. The only way to do this is allow the third parties ip address access so i can publish the content to a domain on my system. Please Help
This suggests the other 2x questions may not apply.
To publish a test/dev/staging site to another IP, requires these steps.
a) cease work on dev site copy, as changes from this point onward will be lost.
b) make a backup of your site, ensuring you've done any related database dumps first.
c) restore the site backup to your live site DocumentRoot.
d) unpack/unzip your backup.
e) create + load any databases.
f) do any site slug (URL) renaming required.
g) repoint your DNS from old site to new site, if required.
Note: Based on your questions, might be good to hire someone for an hour or two to help you go through this process the first time.
1) How do i allow a third party IP Address or domain.com to come thru my firewallD for Centos 7.
This depends on what type of access your trying to grant.
In the case of ssh, you'll have to create a key for them + send them the key + add an iptables rule to allow their IP to access your site or machine.
SFTP will just be an iptables rule.
If you're running a CMS like WordPress, then you'll just add a user with the appropriate role level... so if they're only suppose to be adding content, then their role will be contributor or editor. This depends on WordPress version you're running + how you manage your roles.
Generally this will work...
iptables -I OUTPUT -d 1$ip -j ACCEPT
Be sure to use -I (insert) to place this rule at top of all rules, so it takes precedence.
If you use -A (add) there's a good chance other firewall rules will block the IP before your rule fires.
Also for complex firewall setups, the above will be insufficient. For some firewall setups, you'll require going through all your CHAINS + adding an exception in the correct chain.
2) I need a step by step explanation how to do this.
Same answer as #1. Depend on type of access they require.
Also, if you're running WHM or CPanel steps will be complex. Best hire someone.
Note: WHM + CPanel tend to create complex chains, which will require review to determine correct place to insert your rule or get into your WHM + CPanel docs to determine how to do this or open a support ticket with your hosting company.
3) This is the situation, I have a site builder module installed on my control panel. When i access it, it takes me to the third party company where i do the site creation. Once the site is completed, i have to publish it to a domain on my server. The only way to do this is allow the third parties ip address access so i can publish the content to a domain on my system. Please Help
This suggests the other 2x questions may not apply.
To publish a test/dev/staging site to another IP, requires these steps.
a) cease work on dev site copy, as changes from this point onward will be lost.
b) make a backup of your site, ensuring you've done any related database dumps first.
c) restore the site backup to your live site DocumentRoot.
d) unpack/unzip your backup.
e) create + load any databases.
f) do any site slug (URL) renaming required.
g) repoint your DNS from old site to new site, if required.
Note: Based on your questions, might be good to hire someone for an hour or two to help you go through this process the first time.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.