Ex12.1 Task 3,step 4 Cant access URL after replacing internal IP with public IP
After checking 'public access' and copying the link location to a new browser, according to step 4 internal IP address should be replaced with public address (Eth0). I get the errror "This site cant be reached'..
Comments
-
The two things I would look at for a solution is to ensure the container is shared, and double check your public IP address.
Using the BUI change to a different location and then back. Does the box remain checked, indicating the container has been shared?
What IP address did you use? They are generated each time, so there is no way to know which is accurate for sure. I'd be interested to see which IP range is being issued. You can also obscure the final octet, so it would be something like 12.45.104.xxyy.
Regards,
0 -
The link pointed to different address. I updated the link to eth0 public IP address 104.239.138.xx. I have since closed the lab after completion of the chapter. I can repeat again if you have an suggested resolution steps.
0 -
Hello,
Shoud you return to the lab in the future I'd be happy to try to troubleshoot the issue. If you run the lab again, and have the same issue, please try the above mentioned steps. It looks like you were using the correct IP address. Perhaps a typo? If you remove an extra character from the URL when replacing the IP address it can lead to issues.
Regards,
0 -
my ip is 166.78.174.160 and have successfully logged in the BUI and ssh'd using WSL, so the address is good.
Internal link when right clicking "link" and tested using lynx
http://192.168.98.1:8080/v1/AUTH_17bf4a8c6e9b494ebf4a446edbcfcab6/orders[root@rdo-cc /(keystone_admin)]# lsof -Pni | grep LISTEN | grep 8080
swift-pro 1446 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2730 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2731 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2732 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2733 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2734 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2737 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2738 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)
swift-pro 2739 swift 4u IPv4 24942 0t0 TCP 192.168.98.1:8080 (LISTEN)swift is not listening on external address
edit proxy-server.conf and comment out listen ip
vi /etc/swift/proxy-server.conf
#bind_ip = 192.168.98.1systemctl --list | grep swift-pro
[root@rdo-cc /(keystone_admin)]# systemctl restart openstack-swift-proxy.service
[root@rdo-cc /(keystone_admin)]# lsof -Pni | grep LISTEN | grep 8080
swift-pro 3125 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3145 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3146 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3147 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3148 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3149 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3150 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3151 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)
swift-pro 3152 swift 4u IPv4 1728669 0t0 TCP *:8080 (LISTEN)so internal procedures when setting up lab should not set bind address.
P
0 -
Thank you for the feedback it is helpful to figure out what is going on. After some testing it would appear that the requests are not making it all the way to the instance itself. I have requested the infrastructure team examine the current firewall to see if a port has been blocked recently or any rules have been changed.
From within the instance a netstat -tulpn |grep 8080 shows that swift-proxy is listening to the 192.168.98.1 address. When I upload an object to the container and use elinks from the terminal it does work. But exterior requests seem to fail. This is what elinks look like when I attempt it after creating "testfile":
[centos@rdo-cc ~]$ elinks -dump http://192.168.98.1:8080/v1/AUTH_17bf4a8c6e9b494ebf4a446 edbcfcab6/test12 textfile
I will update you when I hear back from the infrastructure follks.
Best regards,
0 -
As P wrote the issue is which IP address is listening. I had been looking at the issue from the wrong perspective. Updating the errata page until I update the material in general. The steps you will see there will be something like this:
vim /etc/swift/proxy-server.conf .... bind_ip = 0.0.0.0 ... systemctl restart openstack-swift-proxy.service
Then you should be able to see the content. Great catch phiney!
Regards,
0
Categories
- All Categories
- 50 LFX Mentorship
- 103 LFX Mentorship: Linux Kernel
- 553 Linux Foundation Boot Camps
- 296 Cloud Engineer Boot Camp
- 119 Advanced Cloud Engineer Boot Camp
- 52 DevOps Engineer Boot Camp
- 53 Cloud Native Developer Boot Camp
- 4 Express Training Courses
- 4 Express Courses - Discussion Forum
- 1.9K Training Courses
- 18 LFC110 Class Forum
- 6 LFC131 Class Forum
- 25 LFD102 Class Forum
- 150 LFD103 Class Forum
- 17 LFD121 Class Forum
- LFD137 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 598 LFD259 Class Forum
- 102 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 3 LFS203 Class Forum
- 69 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 34 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 92 LFS260 Class Forum
- 130 LFS261 Class Forum
- 32 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS281 Class Forum
- 221 LFW211 Class Forum
- 167 LFW212 Class Forum
- SKF100 Class Forum
- 901 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 761 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 141 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 477 Linux System Administration
- 41 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 66 Mobile Computing
- 23 Android
- 29 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 536 Off Topic
- 131 Introductions
- 216 Small Talk
- 21 Study Material
- 817 Programming and Development
- 275 Kernel Development
- 508 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 59 All In Program
- 59 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)